Spectre bug is back, this time to haunt JIT engines
The vulnerability is found in many CPUs that use speculative execution, the process of executing code before it is called to boost performance. Researchers found speculative execution opens the door to side channel attacks through which secrets can be exposed or inferred.When news of that risk became known, chipmakers and OS developers scrambled to fix these vulnerabilities, which were referred to as Spectre and Meltdown. REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); The attacker trains the branch predictor to execute speculatively to a chosen address in order to leak data about the microarchitecture state.
- ▪The vulnerability is found in many CPUs that use speculative execution, the process of executing code before it is called to boost performance.
- ▪Researchers found speculative execution opens the door to side channel attacks through which secrets can be exposed or inferred.When news of that risk became known, chipmakers and OS developers scrambled to fix these vulnerabilities, which
- ▪REG AD googletag.cmd.push(function() { googletag.display('labrador/thereg/article/desktop/b'); }); The attacker trains the branch predictor to execute speculatively to a chosen address in order to leak data about the microarchitecture state
The Register publishes from United Kingdom and files mainly under tech. We currently carry 776 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | The Register |
| Canonical URL | https://www.theregister.com/security/2026/09/30/spectre-bug-is-back-this-time-to-haunt-jit-engines/5299937 |
| Publication time | Wed, 30 Sep 2026 09:01:00 +0200 |
| Retrieval time | 2026-09-30T07:12:02.933Z |
| Last seen | 2026-09-30T07:12:02.933Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | OE4edNXSAFog · 1 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
(function() { let windowUrl = window.location.href; windowUrl = windowUrl.substring(windowUrl.indexOf('?') + 1); let messageElement = document.querySelector('.shareableMessage'); if (windowUrl && windowUrl.includes('code') && windowUrl.includes('expires')) { messageElement.style.display = 'block'; } })(); security Spectre bug is back, this time to haunt JIT engines Researchers find a way to recover stale indirect branch prediction entries Thomas Claburn Thomas Claburn AI AND SOFTWARE REPORTER Published wed 30 Sep 2026 // 08:01 UTC READ MORE New software dependency validation process increases speeds by 54x 4 days ago Asahi fork embraces LLMs and lands Linux on the M4 Mac mini 4 days ago Decades-old file security flaws found in Android, Linux, macOS, and Windows 5 days ago Talk of AI in…
Excerpt limited to ~120 words for fair-use compliance. The full article is at The Register.
Discussion
0 commentsMore from The Register
