CERTFR-2026-ALE-016
Vulnerability from certfr_alerte - Published: 2026-11-18 - Updated: 2026-11-18
Le 17 novembre 2026, Oracle a publié un avis de sécurité concernant la vulnérabilité CVE-2026-114938, surnommée java4shell, qui affecte le décodeur Base64 de OpenJDK sur les processeurs x86-64 supportant AVX-512 VBMI. Celle-ci permet à un attaquant de provoquer une exécution de code arbitraire à distance et un déni de service à distance.
Cette vulnérabilité ne peut être exploitée qu'en fournissant des données en base64 aux API du composant spécifié sans recourir à des applications Java Web Start ou des applets Java non fiables. Chaque produit affecté nécessite donc une charge utile sur mesure pour être effective.
Cependant, le CERT-FR incite à la vigilance et rappelle que OpenJDK est utilisé dans de nombreux produits, notamment Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, PingFederate, Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, Spinnaker, il est donc important d'appliquer les correctifs de sécurité.
Sous Linux, pour vérifier si le processeur supporte AVX-512 VBMI, la commande suivante peut être lancée :
grep -m1 '^flags' /proc/cpuinfo | tr ' ' '\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'
Contournements provisoires
Le chercheur qui a découvert la vulnérabilité, recommande comme mesures de contournements provisoires de démarrer OpenJDK avec les options XX:-UseBASE64Intrinsics et -XX:UseAVX=2
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Oracle | Java SE | Oracle Java SE version 17.0.21.0.3 | ||
| Oracle | Java SE | Oracle GraalVM for JDK version 21.0.13.0.3 | ||
| Oracle | Java SE | Oracle GraalVM Enterprise Edition version 21.3.20.0.3 | ||
| Oracle | Java SE | Oracle GraalVM for JDK version 17.0.21.0.3 | ||
| Oracle | Java SE | Oracle Java SE version 25.0.5.0.3 | ||
| Oracle | Java SE | Oracle Java SE version 8u511b33-perf | ||
| Oracle | Java SE | Oracle Java SE version 27.0.1.0.3 | ||
| Oracle | Java SE | Oracle Java SE version 21.0.13.0.3 |
| Title | Publication Time | Tags | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Oracle Java SE version 17.0.21.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle GraalVM for JDK version 21.0.13.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle GraalVM Enterprise Edition version 21.3.20.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle GraalVM for JDK version 17.0.21.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle Java SE version 25.0.5.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle Java SE version 8u511b33-perf",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle Java SE version 27.0.1.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "Oracle Java SE version 21.0.13.0.3",
"product": {
"name": "Java SE",
"vendor": {
"name": "Oracle",
"scada": false
}
}
}
],
"affected_systems_content": "",
"closed_at": null,
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-114938",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114938"
}
],
"initial_release_date": "2026-11-18T00:00:00",
"last_revision_date": "2026-11-18T00:00:00",
"links": [
{
"title": "Avis CERT-FR CERTFR-2026-AVI-1562 du 18 novambre 2026",
"url": " /avis/CERTFR-2026-AVI-1562/ "
},
{
"title": "java4shell",
"url": "https://calif.io/java4shell"
}
],
"reference": "CERTFR-2026-ALE-016",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-11-18T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
}
],
"summary": "Le 17 novembre 2026, Oracle a publi\u00e9 un avis de s\u00e9curit\u00e9 concernant la vuln\u00e9rabilit\u00e9 CVE-2026-114938, surnomm\u00e9e *java4shell*, qui affecte le d\u00e9codeur Base64 de OpenJDK sur les processeurs x86-64 supportant AVX-512 VBMI. Celle-ci permet \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance et un d\u00e9ni de service \u00e0 distance.\n\nCette vuln\u00e9rabilit\u00e9 ne peut \u00eatre exploit\u00e9e qu\u0027en fournissant des donn\u00e9es en base64 aux API du composant sp\u00e9cifi\u00e9 sans recourir \u00e0 des applications Java Web Start ou des applets Java non fiables. Chaque produit affect\u00e9 n\u00e9cessite donc une charge utile sur mesure pour \u00eatre effective. \n\nCependant, le CERT-FR incite \u00e0 la vigilance et rappelle que OpenJDK est utilis\u00e9 dans de nombreux produits, notamment Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, PingFederate, Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, Spinnaker, il est donc important d\u0027appliquer les correctifs de s\u00e9curit\u00e9.\n\nSous Linux, pour v\u00e9rifier si le processeur supporte AVX-512 VBMI, la commande suivante peut \u00eatre lanc\u00e9e :\n\u003ccode\u003egrep -m1 \u0027^flags\u0027 /proc/cpuinfo | tr \u0027 \u0027 \u0027\\n\u0027 | grep -E \u0027^(avx512f|avx512bw|avx512vbmi|bmi2)$\u0027\u003c/code\u003e\n\n## Contournements provisoires\nLe chercheur qui a d\u00e9couvert la vuln\u00e9rabilit\u00e9, recommande comme mesures de contournements provisoires de d\u00e9marrer OpenJDK avec les options \u003ccode\u003eXX:-UseBASE64Intrinsics\u003c/code\u003e et \u003ccode\u003e-XX:UseAVX=2\u003c/code\u003e",
"title": "Vuln\u00e9rabilit\u00e9 dans Oracle Java SE",
"vendor_advisories": [
{
"published_at": "2026-11-17",
"title": "Bulletin de s\u00e9curit\u00e9 OpenJDK",
"url": "https://openjdk.org/groups/vulnerability/advisories/2026-11-17"
},
{
"published_at": "2026-11-17",
"title": "Bulletin de s\u00e9curit\u00e9 Oracle",
"url": "https://www.oracle.com/security-alerts/cspunov2026.html"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.