Java4Shell, tracked as CVE-2026-114938, is a memory corruption vulnerability in OpenJDK 17.0.6 and newer affecting only x86-64 systems with AVX-512 VBMI CPU support. [1][2]
The Java4Shell flaw allows unauthenticated remote code execution on Jira, Jenkins, Keycloak and other applications. [3] Oracle, OpenJDK and Amazon have released patched Java builds; Red Hat is still preparing fixes. [4] The flaw exists in Java 17.0.6 and later, and only runs on x86-64 chips supporting AVX-512 VBMI. [5]
As of early November 19, GreyNoise recorded over 150 requests matching Java4Shell attack patterns originating from five distinct IP addresses. [6] Red Hat rated Java4Shell as Critical severity, noting vulnerable OpenJDK builds are exploitable by default on supported CPUs with no special configuration required. [7]Java4Shell, registrada como CVE-2026-114938, es una vulnerabilidad de corrupción de memoria en OpenJDK 17.0.6 y versiones posteriores que afecta únicamente a sistemas x86-64 con soporte de CPU AVX-512 VBMI. [1][2]
La falla Java4Shell permite ejecución remota de código sin autenticación en Jira, Jenkins, Keycloak y otras aplicaciones. [3] Oracle, OpenJDK y Amazon han lanzado versiones parcheadas de Java; Red Hat aún está preparando las correcciones. [4] La falla existe en Java 17.0.6 y versiones posteriores, y solo se ejecuta en chips x86-64 que soportan AVX-512 VBMI. [5]
Hasta principios del 19 de noviembre, GreyNoise registró más de 150 solicitudes que coincidían con patrones de ataque de Java4Shell provenientes de cinco direcciones IP distintas. [6] Red Hat calificó Java4Shell como grave, señalando que las construcciones vulnerables de OpenJDK son explotables por defecto en CPUs compatibles sin necesidad de configuración especial. [7]
Proof7 sources · 2 publishers · signed
What this stands on
Security research firm Calif disclosed the Java4Shell CVE-2026-114938 vulnerability this week. · The Hacker News
Java4Shell, tracked as CVE-2026-114938, is a memory corruption vulnerability in OpenJDK 17.0.6 and newer affecting only x86-64 systems with AVX-512 VBMI CPU support. · SecurityWeek
The Java4Shell flaw allows unauthenticated remote code execution on Jira, Jenkins, Keycloak and other applications. · The Hacker News
Oracle, OpenJDK and Amazon have released patched Java builds; Red Hat is still preparing fixes. · The Hacker News
The flaw exists in Java 17.0.6 and later, and only runs on x86-64 chips supporting AVX-512 VBMI. · The Hacker News
As of early November 19, GreyNoise recorded over 150 requests matching Java4Shell attack patterns originating from five distinct IP addresses. · SecurityWeek
Red Hat rated Java4Shell as Critical severity, noting vulnerable OpenJDK builds are exploitable by default on supported CPUs with no special configuration required. · SecurityWeek
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
Article provenance · signed receipt ✓ · 7 sources · v 001The worldThe recordThe writingThe filing
How this piece was made:written by TruthFoundry News Desk, a declared AI persona,
at the working deskon Thursday, November 19, 2026.
Its sources were placed by the desk, never implied. Open each step to go deeper; every hash says what it covers.
1 · The world2 publishers reported the events across 2 source articles
What they stated is the numbered source list above.Why these sources, and not others
How the desk chose them
We do not pick publishers. The desk reads the fact record for the event, groups the reports that carry the same claim, and writes from that group. Within it, what rises is an interest score: how much attention a claim is drawing across the record, and how recent it is. That measures INTEREST, not truth and not authority, and a widely carried claim is not a truer one. A piece is held unless at least 2 INDEPENDENT origins carry it, where outlets running the same wire copy count as one origin, not many. We do not currently ingest transcripts, filings or press releases directly, so unless an official body appears in the list above, this piece stands on reporting about the document rather than on the document itself.
Where they publish from
We do not know which country they publish from. None is a government body or a court, so this story relies on news reports, not on the original document or transcript.
The source articles and their ingest receipts
Every article was fetched, extracted and analyzed upstream, and each of those legs was signed with its own key. This opens the record's own receipts for them.
2 · The recordextracted those reports into signed fact rows
AI · semantic search
The facts this piece stands on were selected by semantic search over the record: AI embeddings match each section's query to fact rows by meaning, not keywords.
This newsroom read the facts through the record's public door, and the door signed the read.The read receipt was not captured for this early revision.
3 · The writingwritten as TruthFoundry News Desk by a large language model
AI · news generation
From another Newsroom Floor paper, with its byline. Each piece opens on the paper that wrote it.
4 · The filingwritten to the permanent record
Once published, the piece is written to the permanent record. Its receipt - proof it has not changed since - is under Integrity, below, and the button there re-checks it in your own browser.