Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938)
Comments on “Java4Shell: Remote Code Execution in OpenJDK (CVE-2026-114938)”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Security researchers at Datadog Security Labs report CVE-2026-114938, an out-of-bounds write in OpenJDK's optimized Base64 decoder that affects x86-64 systems with AVX-512 VBMI support.
Why it ranked
No. 23 of 142 with a score of 0.71. The panel rated it highest on new information (0.92) and technical depth (0.91), lowest on audience breadth (0.66). Placed No. 23, No. 11 by score alone: the seventh Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Serious, well-substantiated vulnerability analysis with specific technical detail and actionable mitigations; a security advisory affecting many Java deployments, though its scope is bounded by CPU and API conditions.
- AI judgeJudge 3gpt-5.6-luna
- A detailed, reproducible OpenJDK vulnerability analysis explains the faulty AVX-512 path, affected versions and CPUs, exploit constraints, and actionable mitigations. It is highly relevant to Java operators and security engineers, though the RCE framing exceeds the demonstrated evidence somewhat.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.71total under rubric v2.3
- Significance0.69
- Reader interest0.81
- Audience breadth0.66
- Practical relevance0.86
- Substantiated0.81
- Technical depth0.91
- New information0.92
- Counts against: Promotional0.15
- Counts against: Overclaim0.41
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.69 | 0.55 | 0.82 | 0.69 | 0.27 | +0.24 | +0.164 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.77 | 0.72 | 0.93 | 0.81 | 0.21 | +0.26 | +0.210 |
| Audience breadthHow many people who build technology does it concern? | 0.69 | 0.60 | 0.70 | 0.66 | 0.10 | +0.13 | +0.086 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.89 | 0.78 | 0.92 | 0.86 | 0.14 | +0.22 | +0.190 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.73 | 0.80 | 0.90 | 0.81 | 0.17 | +0.05 | +0.040 |
| Technical depthHow technically substantive is it? | 0.99 | 0.80 | 0.94 | 0.91 | 0.20 | +0.05 | +0.046 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.88 | 0.90 | 0.99 | 0.92 | 0.11 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.08 | 0.20 | 0.18 | 0.15 | 0.12 | −0.19 | −0.029 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.52 | 0.30 | 0.42 | 0.41 | 0.22 | −0.11 | −0.045 |
| Sum of contributions | +0.708 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.708 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-18/23/"><img src="https://rubric.hrih.si/badge/2026-11-18/23.svg" alt="Ranked #23 on Rubric, 18 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 no source given · 6 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Couldn’t checkDate
Oracle released a security update for CVE-2026-114938, an out-of-bounds write in OpenJDK's optimized Base64 decoder, on November 17, 2026.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “On November 17, 2026, Oracle released a security update for CVE-2026-114938, an out-of-bounds write in OpenJDK’s optimized Base64 decoder”
The source says No passage could be compared.
Source cited by the article: oracle.com/security-alerts/cspunov2026.html
Couldn’t checkNumber
CVE-2026-114938 affects OpenJDK 17.0.6 and later and is rated 9.2 (Critical) under CVSS 4.0.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “This vulnerability affects OpenJDK 17.0.6 and later and has been rated 9.2 (Critical) under CVSS 4.0”
The source says No passage could be compared.
Source cited by the article: oracle.com/security-alerts/cspunov2026.html
Couldn’t checkVersion
Java 17 releases from 17.0.6 up to versions before 17.0.21.1 are affected, with 17.0.21.1+4 the first fixed release.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Java 17 17.0.6 through versions before 17.0.21.1 17.0.21.1+4”
The source says No passage could be compared.
Source cited by the article: oracle.com/java/technologies/javase/17-0-21-1-relnotes.html
Couldn’t checkVersion
All Java 21 versions before 21.0.13.1 are affected, with 21.0.13.1+4 the first fixed release.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Java 21 All versions of Java 21 before 21.0.13.1 21.0.13.1+4”
The source says No passage could be compared.
Source cited by the article: oracle.com/java/technologies/javase/21-0-13-1-relnotes.html
No source givenGeneralization
In the tested OpenJDK 17.0.6 build, the AVX-512 path handles the basic and URL decoders, while the MIME decoder bypasses it.
The article gives no link or citation for it.
The article says “the AVX-512 path handles the basic and URL decoders returned by Base64.getDecoder() and Base64.getUrlDecoder(). The MIME decoder returned by Base64.getMimeDecoder() bypasses this path”
The source says No source to compare with.
Couldn’t checkCausal conclusion
The malformed value of 128 'A' characters followed by '=' produces a destination length of 98 bytes, and the tail handler's output count becomes -1 because there is no nonnegative check.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “There is no check that the result remains nonnegative, so the count becomes -1”
The source says No passage could be compared.
Source cited by the article: github.com/openjdk/jdk17u/blob/2fe42855c48c49b515b97312ce64a5a8ef3af407/src/hotspot/cpu/x86/stubGenerator_x86_64.cpp
No source givenCausal conclusion
Starting the JVM with -XX:UseAVX=2 or -XX:-UseBASE64Intrinsics prevented the out-of-bounds writes in the authors' tests.
The article gives no link or citation for it.
The article says “our tests confirmed two JVM startup options that prevented the out-of-bounds writes”
The source says No source to compare with.
Couldn’t checkCausal conclusion
Native ARM64 JVMs do not recognize the UseAVX=2 option, and passing it can prevent ARM64 services from starting.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Native ARM64 JVMs do not execute the vulnerable code, and they do not recognize this option. Adding it to shared startup settings can prevent ARM64 services from starting”
The source says No passage could be compared.
Source cited by the article: docs.oracle.com/en/java/javase/17/docs/specs/man/java.html
Also covered by
Elsewhere
Elsewhere: HN —
Recorded for context only, checked 18 Nov 2026, 05:47 UTC. It played no part in the ranking.