Overview
- Oracle Corporation
- Oracle Java SE
Description
Statistics
- 108 Posts
- 289 Interactions
Fediverse
Yes, we are tracking the potential RCE vulnerability in Java. No, we are not using the marketing name except as a tag. Details and facts here as they are available.
https://ifin.network/t/cve-2026-114938-pre-auth-remote-code-execution-in-java/997
"After we disclosed PHP2Shell, we realized many people didn't know what PHP was. So we decided to go after something a little more familiar: Java."
Calif.io Clearly setting their priorities as publicity-maxxing, therefor gotta name it "<whatever>[2|4]shell".
Java CVE-2026-114938 pre-auth RCE via memory-corruption vulnerability in OpenJDK's Base64 decoder.
Dzień (nie taki) dobry! ⚠️ Jeśli macie Javę (a pewnie gdzieś macie) pora panikować. Ogłoszono nowa krytyczną dziurę RCE - Java4Shell (CVE-2026-114938; CVSS 4.0 = 9.2)
Zagrożona jest praktycznie każda aplikacja Java na Intel Ice Lake+ lub AMD Zen 4+. Czyli takie apki jak:
☢️ Jira, Confluence, Jenkins, Keycloak, Artifactory, Kafka i wiele innych.
‼️Część da się zaatakować bez uwierzytelnienia.
Problem leży w dekoderze Base64 w OpenJDK (od wersji 17.0.6, plus 21, 25 i 27) czyli dotyczy też dystrybucji (Corretto, Temurin, Azul, Liberica, Oracle Java SE itp.).
Odpowiedni ciąg Base64 (np. ciąg "A" zakończony 😊 przy odpowiednim ułożeniu sterty może spowodować wykonanie kodu atakującego.
Na szczęście:
❌ Nie dotyczy ARM64
❌ Nie dotyczy starszych x86 bez AVX-512 VBMI (przed Ice Lake/Zen 4)
❌ Nie dotyczy standardowej Javy 8 i 11 (poza specjalnym buildem Performance Pack)
Co robić, jak żyć?
✅ Zaktualizujcie Javę do wersji (17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1) łatki właśnie udostępniono
🟧 albo dodajcie:
-XX:-UseBASE64Intrinsics lub -XX:UseAVX=2
Pamiętajcie o Javie schowanej w Dockerach itp.!
⚠️ THIS IS NOT A DRILL!
#Java4Shell CVE-2026-114938
If you're running Java based systems on modern x64 CPUs you'll likely need to act.
Calif has discovered an unauthenticated remote code execution (RCE) vulnerability in the OpenJDK's Base64 decoder.
Technically, it's a memory corruption vulnerability and affects the optimized code path of Java's built-in Base64 decoder making use of AVX-512 instructions.
Thus JVMs running on more modern CPUs like AMD EPYC Zen 4 or later and Intel Xeon Ice Lake/Sapphire Rapids/Emerald Rapids and Granite
Rapids are affected by this vulnerability.
Java's built-in Base64 Decoder is used everywhere these days and is especially widely used in combination with untrusted data coming from
HTTP Basic Auth, SAML, Cookies, JWTs, etc.
Calif was able to exploit following popular Java applications without needing authentication:
* Atlassian Confluence + Jira
* Jenkins
* Keycloak (IAM)
* PingFederate (IAM)
and more
Watch them exploiting different applications here:
https://www.youtube.com/watch?v=-EOYmL4UKvs
Fix:
For a complete fix update affected JDKs. (Oracle Critical Security Patch Update from November 17th, CVE-2026-114938)
Mitigation:
Per Calif's blog post the vulnerability can be mitigated by starting affected JVMs on x64 systems with the parameters:
-XX:-UseBASE64Intrinsics
or
-XX:UseAVX=2
(This command-line flag restricts the HotSpot JIT compiler to using AVX2 vector instructions instead of higher instruction sets like AVX-512.)
Read more in Calif's blog post:
https://calif.io/java4shell
Hinweise von Keycloak Team
https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938 #java4Shell
Y'all have fun waiting on your vendors to determine impact from CVE-2026-114938 while they prioritize more acquisitions, AI bullshit, and of course deflecting blame for their outages.
Java4Shell (CVE-2026-114938) affects Java software worldwide.
Our status:
• Desktop: update to Cryptomator 1.19.7, which applies the recommended mitigation.
• Mobile: the iOS and Android apps are not affected.
• Hub (managed): not affected, no action required.
• Hub (self-hosted): Hub is not affected. Keycloak can be, depending on the CPU. Update to our Keycloak image 26.8.2.1.
All details and instructions:
https://cryptomator.org/blog/2026/11/18/java4shell/?utm_source=mastodon&utm_medium=social&utm_campaign=java4shell
⚠️📢 Oracle has patched Java4Shell (CVE-2026-114938). Researchers demonstrated that the OpenJDK flaw can let attackers run code on affected Java servers without logging in.
Listen/Read/Watch Demo: https://hackread.com/java4shell-flaw-run-code-java-servers-logging-in/
Hello Java4shell https://calif.io/java4shell/
CVE-2026-114938: (9.2 critical) memory corruption in OpenJDK Java runtime.
We discovered a bug in that optimized machine-level code that lets malformed input overwrite neighboring memory. With careful exploitation, the corruption can reveal sensitive memory, as Heartbleed did, or lead to remote code execution. The corruption itself can be triggered by just 64 A characters followed by a single =:
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=
https://www.cve.org/CVERecord?id=CVE-2026-114938
Interestingly Oracle scored it much lower at 8.1 high severity. https://www.oracle.com/security-alerts/cspunov2026.html
There it is. https://calif.io/java4shell/ #CVE_2026_114938
Guten Morgen, liebe Kund*innen! Unsere #Keycloak App ist von CVE-2026-114938 betroffen. Hier haben wir eine Infoseite für Euch, was Ihr tun könnt, bis ein Keycloak-Update kommt:
Nach #PHP2Shell jetzt auch noch #Java4Shell - Wir können aber schon einmal Entwarnung geben: Betroffene Hosting-Dienste sind bei uns bereits mit Schutzmaßnahmen versehen.
Mehr Infos zur Schwachstelle Java4Shell: https://thehackernews.com/2026/11/java4shell-cve-2026-114938-enables-pre.html
Java4Shell (CVE-2026-114938) is a heap overflow in the JDK's Base64 decoder. It gives attackers code execution without login on Keycloak, Jenkins, Jira, Confluence, Artifactory and PingFederate.
Exposed: Java 17, 21, 25 and 27 on x86-64 CPUs with AVX-512 VBMI. ARM and Java 11 are not affected. No exploitation reported as of 18 November.
Update Java. Until you can, our free CrowdSec WAF rule blocks the malformed Base64 that triggers it:
https://www.crowdsec.net/blog/java4shell-virtual-patching
Serious warning: “🚨We urge orgs to immediately patch the recently disclosed #Oracle #Java vuln CVE-2026-114938. This critical memory-corruption #vulnerability, known as “#Java4Shell,” affects the Base64 decoder of the x86-64 HotSpot JVM, part of the Java Development Kit. 🔗go.dhs.gov/5CC
Java4Shell: Kritische Lücke in OpenJDK
Die Sicherheitsexperten von Calif haben mit „Java4Shell“ (CVE-2026-114938) eine kritische Schwachstelle vom Typ „Memory Corruption“ im Base64-Decoder von OpenJDK entdeckt.
https://www.linux-magazin.de/news/java4shell-kritische-luecke-in-openjdk/
Security researchers say Java4Shell (CVE-2026-114938) can let attackers execute code on vulnerable Java services without logging in. Admins should check bundled runtimes and patch affected systems; disabling Base64 intrinsics is only a temporary workaround. 🔐⚠️ cyberinsider.com/java4shell-java-flaw-remote-code-execution-without-login/ #Java #Cybersecurity
There’s a vulnerability in #Java.
Mitigation: stop your node, go into wrapper.conf, add a line like
wrapper.java.additional.10=-XX:-UseBASE64Intrinsics
(use the next number of your arguments instead of 10 if needed)
Then start the node again.
This should prevent attacks until there’s a Java update.
Alternative: shut down your node. Only let it start again once there are Java updates. ⇒ Browsing (welcome page) ⇒ Version Information & Node Control ⇒ Shutdown Freenet.
🚨 Java4Shell (CVE-2026-114938) could enable remote code execution and memory disclosure in affected OpenJDK installations.
Researchers report exploitation in popular enterprise applications. All Java users should update immediately.
This is a developing issue. We’ll update this advisory as new information emerges. https://censys.com/advisory/cve-2026-114938/
#Java4Shell #OpenJDK #JavaSecurity #CVE2026114938 #RemoteCodeExecution #VulnerabilityManagement #CyberSecurity #ThreatIntelligenc
🚨 Critical Java4Shell vulnerability allows hackers to remotely execute code in Jira, Confluence, Jenkins, and other major platforms; CVE-2026-114938
YouTube Video (attached): https://www.youtube.com/watch?v=-EOYmL4UKvs
Security researchers at Calif have disclosed a critical OpenJDK vulnerability (CVSS 9.2) that could allow unauthenticated attackers to steal sensitive server memory and execute malicious code remotely.
Dubbed Java4Shell, the flaw affects OpenJDK's Base64 decoder. Researchers successfully demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, JFrog Artifactory, and PingFederate in their default configurations.
The vulnerability affects supported Java distributions running on certain x86-64 processors with AVX-512 support. Researchers used AI to discover the flaw in approximately one hour and develop a working exploit in two more hours.
Security updates are now available. Administrators are urged to patch immediately or disable the vulnerable Base64 optimization.
Source: https://calif.io/java4shell/
Java4Shell, ritische Schwachstelle (CVE-2026-114938) in JAVA (OpenJDK 17.0.6+)
https://borncity.com/blog/2026/11/17/kritische-schwachstelle-java4shell-cve-2026-114938/
🚨 Java4Shell PoC released for critical OpenJDK vulnerability that could allow remote code execution; CVE-2026-114938
PoC: https://github.com/ikow/java4shell-poc
A public proof-of-concept has been released for Java4Shell, a critical memory corruption vulnerability in OpenJDK's Base64 decoder that could allow unauthenticated attackers to execute malicious code on affected Java servers.
Researchers have demonstrated remote code execution against Keycloak, Jira, Confluence, Jenkins, Artifactory, and PingFederate. Exploitation requires compatible x86-64 processors supporting AVX-512 VBMI.
CVSS: 9.2 Critical (v4.0)
Affected: OpenJDK 17, 21, 25, and 27 on supported hardware
Fixed: 17.0.21.1, 21.0.13.1, 25.0.5.1, and 27.0.1.1
The PoC includes a heap corruption reproducer, vulnerability scanners, detection rules, and a Docker testing environment. It does not include a complete remote code execution exploit.
💥 No delays. No guessing. No redactions. Get the intel threat actors see, the moment they post it. Crypto friendly. darkwebinformer.com/pricing
Need API access? darkwebinformer.com/api-details
Check out the Telegram channel: t.me/SliceForLifeee
Java4Shell CVE-2026-114938: Fine, I Guess We’ll Do This Again | Blog | VulnCheck https://www.vulncheck.com/blog/java4shell
Java update for critical vulnerability dropping in less than an hour. Let’s hope it’s an overhyped nothingburger in a rarely used feature… https://thehackernews.com/2026/11/oracle-to-patch-11-java-flaws-today-as.html
TR-104 - Critical Memory Corruption in OpenJDK Base64 Decoder (Java4Shell, CVE-2026-114938)
The TR document includes all the technical details, vulnerable software and it will be regularly updated.
Release wohl 22:00
19e1b44520669be6269a485a3f361de95e800e68cb6d880285f5d5f4b34bf10f
"Critical Pre-authentication Remote Code Execution in #Java 17"
CVE-2026-114938
#Java: Critical #Java4Shell #vulnerability CVE-2026-114938, allows #RCE attacks on major Java applications!
Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, and PingFederate among impacted with unauth RCE:
👇
Cisco Talos is closely tracking the disclosure of Java4Shell (CVE-2026-114938) in OpenJDK Java, which may lead to unauthenticated remote code execution. Find more details and coverage in our blog: https://blog.talosintelligence.com/java4shell/
GreyNoise is tracking Java4Shell (CVE-2026-114938) with a live dashboard here: https://java4shell.events.greynoise.io/
At this time, we are not aware of successful exploitation in the wild. We believe this will be challenging to mass exploit at least initially due to the need for the exploit to be tailored for each targeted system build.
Are people actually seeing exploitation attempts, blocked or otherwise, for #Java4Shell / #CVE2026114938?
Jitsi Meet has been disabled due to CVE-2026-114938 (https://www.cve.org/CVERecord?id=CVE-2026-114938) https://calif.io/java4shell/
It will brought back when the CVE is fixed in Nixpkgs, as I use NixOS on the servers, lol.
Patch Java4Shell!
Calif researcher Quang Luong said they discovered CVE-2026-114938 while “developing a 0-click exploit on a certain phone vendor.”
Java4Shell (CVE-2026-114938) is a reported unauthenticated RCE in OpenJDK 17.0.6 and later, scored 9.2 under CVSS 4.0. The flaw is in the runtime, so manifest-based dependency scans won't surface it.
www.endorlabs.com/learn/java4shell-unauthenticated-rce-reported-in-openjdk-17-cve-2026-114938
#infosec #java #openjdk #appsec
We've just pushed a mitigation for the Java RCE vulnerability published an hour ago (CVE-2026-114938). We recommend upgrading your servers as soon as possible.
The Java4Shell vulnerability lets attackers run code on Java servers with AVX-512 CPUs. See affected apps, 10 more Oracle Java fixes and steps to take now.
#Java4Shell #Java #OpenJDK #Oracle #CyberSecurity #CVE2026114938
Java4Shell (CVE-2026-114938): Ejecución remota de código sin autenticación en Jira, Jenkins y Keycloak sobre servidores Java 17+ con AVX-512 VBMI
https://blog.elhacker.net/2026/11/java4shell-cve-2026-114938-ejecucion.html
Java4Shell (CVE-2026-114938): overflow nel decoder Base64 accelerato di OpenJDK. Calif: RCE senza autenticazione su Keycloak, Jira, Confluence, Artifactory, Jenkins e PingFederate in configurazione predefinita. Exploit non pubblicati. Nessuno sfruttamento noto, non in KEV.
Colpite Java 17.0.6 e successive, 21, 25, 27 (non 8 e 11 standard), solo su x86-64 con AVX-512 VBMI. Patch Oracle e OpenJDK del 17/11; mitigazione temporanea -XX:-UseBASE64Intrinsics.
https://thehackernews.com/2026/11/java4shell-cve-2026-114938-enables-pre.html
#Java
Java4Shell (CVE-2026-114938): A Critical Java Vulnerability with a Surprisingly Small Fix. https://www.tutego.de/blog/javainsel/2026/11/java4shell-cve-2026-114938-a-critical-java-vulnerability-with-a-surprisingly-small-fix-3700728c/ #Java #OpenJDK #JavaSecurity #CVE2026114938 #InfoSec #Semgrep
La faille Java4Shell (CVE-2026-114938) menace Keycloak, Jira, Jenkins, etc. https://www.it-connect.fr/java4shell-faille-critique-java-openjdk/ #ActuCybersécurité #Cybersécurité #Vulnérabilité
⚠️ Alerte CERT-FR ⚠️
La vulnérabilité CVE-2026-114938 (java4shell) permet une exécution arbitraire à distance dans Java SE, sous certaines conditions.
https://cert.cyber.gouv.fr/alerte/CERTFR-2026-ALE-016/
Critical Java4Shell flaw allows RCE attacks on major Java applications
A critical memory-corruption flaw in OpenJDK’s hardware-accelerated Base64 decoding — CVE-2026-114938, dubbed Java4Shell and rated 9.2 by the Calif researchers who found it — can be triggered with a short crafted Base64 string on AVX-512 systems, and the researchers demonstrated unauthenticated remote code execution against Keycloak, Jira, Confluence, Jenkins and other widely used Java applications running default configurations. Oracle patched the flaw on November 17 in its November Critical Patch Update; until runtimes are updated, disabling the Base64 intrinsics is the recommended workaround. https://www.bleepingcomputer.com/news/security/critical-java4shell-flaw-allows-rce-attacks-on-major-java-applications/
A severe vulnerability dubbed Java4Shell (CVE-2026-114938) has been discovered in OpenJDK's Base64 decoder, impacting systems running on x86-64 processors with AVX-512 VBMI support.
The flaw permits unauthenticated remote code execution, JVM crashes, or sensitive memory exposure depending on the default configuration of popular Java platforms.
Oracle released out-of-band updates on November 17, 2026, and CISA advised immediate pa…
https://en.hacks.gr/keno-asfaleias-sto-openjdk-epitrepei-apomakrysmeni-ektelesi-kodika/
Voili, voilà… nous avons donc un nouveau truc en « -Shell », cette fois dans sa version Java4Shell .
La vulnérabilité CVE-2026-114938 a été découverte par le chercheur Quang Luong (Calif), avec l'aide de Codex. Que cela plaise ou non dans l'arène des anti-IA, des pro-IA et des agnostiques.
👇
https://calif.io/java4shell/
La faille touche un mécanisme utilisé par Java pour décoder certaines données (Base64).
Les chercheurs ont démontré qu'elle pouvait permettre de prendre le contrôle à distance de serveurs utilisant des applications comme Jira, Jenkins ou Keycloak, parfois sans même disposer d'un compte utilisateur.
Mais alléluia, tous les serveurs Java ne sont pas vulnérables ! 🙌
L'exploitation nécessite une version de Java affectée, un processeur compatible AVX-512 VBMI et une application permettant de traiter des données piégées envoyées par l'attaquant.
--> Vérifier les versions de Java, y compris celles intégrées aux logiciels, appliances et conteneurs, puis appliquer les correctifs disponibles.
En attendant, l'option -XX:-UseBASE64Intrinsics permet de désactiver le mécanisme vulnérable (mesure temporaire nécessitant un redémarrage).
À ce stade, pas de preuve d'exploitation malveillante dans la nature.
🎧 Écoute musicale conseillée en attendant ou en patchant : grin & bear it — Panic Shack ! :)
👇
https://panicshack.bandcamp.com/track/grin-bear-it
Java4Shell (CVE-2026-114938): Speicherfehler in OpenJDK ermöglicht Remote-Code-Ausführung
Im Base64-Decoder von OpenJDK steckt ein Speicherfehler, der Angreifern ohne Anmeldedaten die Ausführung von Code aus der Ferne ermöglichen kann.
CISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution
CISA has urged organisations to immediately patch a newly disclosed critical flaw in Oracle Java, tracked as CVE-2026-114938 and dubbed Java4Shell. The memory-corruption flaw is an out-of-bounds write that can lead to denial of service or remote code execution under certain conditions. https://thehackernews.com/2026/11/cisa-urges-immediate-patching-of.html
#SSI #Java
Une faille Java (Java4Shell / CVE-2026-114938) de niveau élevé (score 8.1 sous CVSS 3.1) à critique (score 9,2 sous CVSS 4.0), qui impacte les versions Oracle des VM Java, mais pas seulement : a priori toutes les distributions s'appuyant sur OpenJDK, telles que les distributions d''Eclipse, d'Amazon, de Microsoft... :
- https://www.tenable.com/blog/java4shell-cve-2026-114938-frequently-asked-questions-about-openjdk-rce-vulnerability#i-don-t-use-oracle-s-java-builds-am-i-affected
- https://www.tenable.com/cve/CVE-2026-114938
65 Characters to RCE: Inside the Java4Shell Vulnerability
#Keycloak Java4Shell vulnerability:
"If your organization uses Keycloak, please pass this post to the team that operates it, even if you do not run Keycloak yourself. They need to check the Java runtime and the CPU type used by every Keycloak instance. The issue is CVE-2026-114938, known as Java4Shell." https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938
Yes, another “4Shell.” 😬 But #Java4Shell (CVE-2026-114938) doesn’t hit every Java server, and that changes how you triage it.
According to Calif, the team that found it, it leads to pre-auth RCE in Keycloak, Jira, Confluence, Artifactory, Jenkins, and PingFederate, all in default configurations.
It only bites when four things line up: an affected JVM (Java 17, 21, 25, or 27), an x86-64 CPU with AVX-512 VBMI, untrusted Base64 reaching the decoder, and a JIT-compiled decoder. Two of those are invisible from the outside.
Our deep dive covers affected and fixed builds, the root cause, what’s confirmed vs. claimed, and how to mitigate safely: https://pentest-tools.com/blog/java4shell-cve-2026-114938
Oracle issued a Java security patch on November 17 after researchers disclosed a vulnerability that could allow attackers to compromise Jira, Jenkins, and several other services without signing in.
The flaw has been dubbed Java4Shell (CVE-2026-114938), and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) has urged organizations to patch immediately.
We are updating our packages to fix #java4shell #CVE-2026-114938 . See https://forum.cloudron.io/topic/16303/java4shell-cve-2026-114938/3 for more information .
Neu Warnung:
Kritische Sicherheitslücke in Java (Java4Shell) - Updates verfügbar - CVE-2026-114938 https://www.cert.at/de/warnungen/2026/11/kritische-sicherheitslucke-in-java-java4shell-updates-verfugbar-cve-2026-114938
📰 CISA Issues Urgent Warning for Critical "Java4Shell" RCE Flaw
🚨 URGENT: CISA warns of critical "Java4Shell" RCE flaw (CVE-2026-114938) in OpenJDK/Oracle Java. Unauthenticated heap overflow in Base64 decoder affects Jira, Confluence, Jenkins & more. CVSS 9.2. Patch immediately! #Java #CyberSecurity #Vulnerability
Java2Shell (CVE-2026-114938)
Na bijna 15 2Shell-lekken en bijhorende exploits in bijna elke technologie waarop onze moderne informatiemaatschappij gebouwd is, van WordPress en PHP tot de Brotli-compressie, is het nu ook prijs voor de COBOL van mijn generatie: Java.
Bluesky
Overview
Description
Statistics
- 30 Posts
- 74 Interactions
Fediverse
🚨 NGINX enjoyers, there's a CRITICAL SECURITY ISSUE and you MUST immediately upgrade to the latest version (e.g. OSS 1.30.7):
(generally you should keep on top of the NGINX versions)
Rapid7 says the attack needs roughly 128 GB of HTTP/2 traffic over one connection: about two minutes at 10 Gbit/s, about seventeen at 1 Gbit/s, probably not achievable below about 300 Mbit/s. Proxied HTTP/2 connections will probably not work.
Why are we treating this like the world is on fire?
If you got bored with the Java RCE because that's just so yesterday's news, here, enjoy two more NGINX RCEs (CVE-2026-123633, HTTP/2 connection use-after-free; and CVE-2026-123007 HTTP/2 send_window integer underflow):
CVE-2026-123007 enables NGINX remote code execution over HTTP/2, and a public PoC exploit is out. Affected versions, limits and fixes.
#NGINX #CVE2026123007 #HTTP2 #RCE #PoC #PatchNow #CyberSecurity #InfoSec
NGINX2Root (CVE-2026-123007) lets attackers run code on NGINX servers with HTTP/2 enabled. Five flaws, a public PoC, and how to patch.
#NGINX2Root #NGINX #HTTP2 #RCE #PoC #PatchNow #CyberSecurity #InfoSec
🚨 Five critical NGINX vulnerabilities expose millions of web servers to remote code execution and potential root takeover
PoC: https://github.com/sfewer-r7/CVE-2026-123007
Security researchers at Xint have disclosed NGINX2Root, a collection of five critical NGINX vulnerabilities that could allow unauthenticated attackers to execute malicious commands on affected web servers.
The most severe flaw, CVE-2026-123007, affects NGINX servers with HTTP/2 enabled and has existed since 2015. Researchers demonstrated how it could be chained with a separate Linux kernel vulnerability to gain full root access, even escaping Docker containers.
According to Xint, approximately 11.8 million servers run NGINX versions within the affected range. Version 1.31.9 addresses the NGINX flaws, while the Linux kernel vulnerability requires a separate fix. No active exploitation has been confirmed.
Source: https://nginx2root.com/
Both Wiz and Rapid7 drop vulnerability details and proofs of concept for CVE-2026-123007 and Wiz has CVE-2026-123633:
- https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
CVE-2026-123633 has different exploitation constraints and is more likely to be exploited when NGINX is configured in proxy configuration.
Beveiligingsupdate toot.re
Vandaag zijn twee ernstige lekken in nginx bekendgemaakt (CVE-2026-123007 en CVE-2026-123633). nginx is de webserver die voor deze Mastodon-server staat.
Wat ik gedaan heb:
✅ Alle beschikbare beveiligingsupdates geïnstalleerd
✅ HTTP/2 tijdelijk uitgezet; dat blokkeert beide lekken
Voor jullie verandert er niets. Zodra Ubuntu een patch uitbrengt, installeren we die.
Uitleg: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
⚠️ NGINX2Root : plusieurs RCE sans authentification, dont CVE-2026-123007 et CVE-2026-123633.
Et pour faire bonne mesure, les chercheurs de Xint ont enchaîné avec une autre vulnérabilité, cette fois dans le noyau Linux (SCTP), pour passer de NGINX à root sur l'hôte, y compris en s'échappant d'un conteneur Docker. 😭
🐧 Côté distributions Linux, notamment Debian 12/13 et RHEL 8/9/10, les correctifs restent à confirmer. Attention aux rétroportages !
✅ NGINX corrigé : 1.30.7 / 1.31.9
🩹 En attendant : désactiver HTTP/2 après vérification des dépendances (gRPC notamment).
Cela ne couvre pas toutes les failles.
Et pour les amateurs de démonstrations qui piquent, la GIF des chercheurs de Xint vaut le détour.
👇
https://xint.io/blog/nginx2root-remote-code-execution
(Bande-son conseillée pour accompagner: Roots Bloody Roots
par ...Chat Pile ;) https://chatpile.bandcamp.com/album/roots-bloody-roots)
Disabling http/2 support for now (nginx-http2-rce-vulnerabilities)
http/2 support has been disabled while we investigate the impact of two nginx CVEs:
https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
https://www.cve.org/CVERecord?id=CVE-2026-123633
https://www.cve.org/CVERecord?id=CVE-2026-123007
Everything should fall back to http/1.1 which is slightly less efficient, but everything should keep working.
This impacts sourceware.org, cygwin.org, dwarfstd.org, elfutils.org, gcc.gnu.org, systemtap.org, valgrind.org and various subdomains.
⚠️ Security Advisory: Critical Nginx vulnerabilities (NGINX2Root, incl. CVE-2026-123007 & CVE-2026-123633) were disclosed today.
Passbolt Cloud: Not affected. No action needed.
Self-Hosted Passbolt: Affected. Require immediate configuration changes.
Status & mitigation instructions: https://passboltstatus.com/
☠️ EXECUÇÃO REMOTA DE CÓDIGO NÃO AUTENTICADO NO NGINX: CVE-2026-123633 E CVE-2026-123007
No capítulo de hoje da distopia de segurança da informação, duas falhas críticas via HTTP/2 podem permitir que invasores comprometam os populares servidores web NGINX, colocando em risco os sites, APIs e dados confidenciais que eles manipulam.
Sites e APIs podem ser expostos mesmo se o seu próprio código for seguro.
Two serious NGINX flaws, CVE-2026-123633 and CVE-2026-123007, were disclosed on 18 November 2026.
Both require NGINX to accept HTTP/2 connections, and exposure depends on version and configuration.
Wiz demonstrated code execution for CVE-2026-123007 on NGINX serving static files alone; affected Open Source versions range from 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8.
Versions 1.30.7 and 1.31.9 fix both flaws.
Use in attacks a…
We've just pushed a mitigation for the Nginx RCE vulnerability published an hour ago (CVE-2026-123007 and CVE-2026-123633). We recommend upgrading your servers as soon as possible.
NGINX shipped 1.31.9 (mainline) and 1.30.7 (stable) today with fixes for 10 CVEs. The two to care about: CVE-2026-123633 and CVE-2026-123007, HTTP/2 memory bugs that Wiz says allow unauthenticated remote code execution (CVSS 4.0 9.2). One reaches back to 1.9.5 from 2015. Exploitation needs HTTP/2 on. No in-the-wild attacks reported so far. Upgrade, or turn off HTTP/2 until you can.
NGINX HTTP/2 RCE Vulnerabilities (CVE-2026-123633 and CVE-2026-123007): Technical Analysis and How to Patch
Critical NGINX HTTP/2 vulnerability pair (CVE-2026-123633, CVE-2026-123007) allows unauthenticated RCE. How they work, affected versions, and how to patchhttps://thecybersecguru.com/exploits/nginx-http2-vulnerability-cve-2026-123633-123007/
> The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2. The flaws are in NGINX itself. Websites and APIs can be exposed even when their own application code is secure. Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. Additional conditions are described below. CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015.
#infosec #rce #vulnerability
https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
Bluesky
Overview
- F5
- NGINX Open Source
Description
Statistics
- 22 Posts
- 92 Interactions
Fediverse
If you got bored with the Java RCE because that's just so yesterday's news, here, enjoy two more NGINX RCEs (CVE-2026-123633, HTTP/2 connection use-after-free; and CVE-2026-123007 HTTP/2 send_window integer underflow):
Both Wiz and Rapid7 drop vulnerability details and proofs of concept for CVE-2026-123007 and Wiz has CVE-2026-123633:
- https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
CVE-2026-123633 has different exploitation constraints and is more likely to be exploited when NGINX is configured in proxy configuration.
Beveiligingsupdate toot.re
Vandaag zijn twee ernstige lekken in nginx bekendgemaakt (CVE-2026-123007 en CVE-2026-123633). nginx is de webserver die voor deze Mastodon-server staat.
Wat ik gedaan heb:
✅ Alle beschikbare beveiligingsupdates geïnstalleerd
✅ HTTP/2 tijdelijk uitgezet; dat blokkeert beide lekken
Voor jullie verandert er niets. Zodra Ubuntu een patch uitbrengt, installeren we die.
Uitleg: https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
⚠️ NGINX2Root : plusieurs RCE sans authentification, dont CVE-2026-123007 et CVE-2026-123633.
Et pour faire bonne mesure, les chercheurs de Xint ont enchaîné avec une autre vulnérabilité, cette fois dans le noyau Linux (SCTP), pour passer de NGINX à root sur l'hôte, y compris en s'échappant d'un conteneur Docker. 😭
🐧 Côté distributions Linux, notamment Debian 12/13 et RHEL 8/9/10, les correctifs restent à confirmer. Attention aux rétroportages !
✅ NGINX corrigé : 1.30.7 / 1.31.9
🩹 En attendant : désactiver HTTP/2 après vérification des dépendances (gRPC notamment).
Cela ne couvre pas toutes les failles.
Et pour les amateurs de démonstrations qui piquent, la GIF des chercheurs de Xint vaut le détour.
👇
https://xint.io/blog/nginx2root-remote-code-execution
(Bande-son conseillée pour accompagner: Roots Bloody Roots
par ...Chat Pile ;) https://chatpile.bandcamp.com/album/roots-bloody-roots)
Disabling http/2 support for now (nginx-http2-rce-vulnerabilities)
http/2 support has been disabled while we investigate the impact of two nginx CVEs:
https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
https://www.cve.org/CVERecord?id=CVE-2026-123633
https://www.cve.org/CVERecord?id=CVE-2026-123007
Everything should fall back to http/1.1 which is slightly less efficient, but everything should keep working.
This impacts sourceware.org, cygwin.org, dwarfstd.org, elfutils.org, gcc.gnu.org, systemtap.org, valgrind.org and various subdomains.
⚠️ Security Advisory: Critical Nginx vulnerabilities (NGINX2Root, incl. CVE-2026-123007 & CVE-2026-123633) were disclosed today.
Passbolt Cloud: Not affected. No action needed.
Self-Hosted Passbolt: Affected. Require immediate configuration changes.
Status & mitigation instructions: https://passboltstatus.com/
☠️ EXECUÇÃO REMOTA DE CÓDIGO NÃO AUTENTICADO NO NGINX: CVE-2026-123633 E CVE-2026-123007
No capítulo de hoje da distopia de segurança da informação, duas falhas críticas via HTTP/2 podem permitir que invasores comprometam os populares servidores web NGINX, colocando em risco os sites, APIs e dados confidenciais que eles manipulam.
Sites e APIs podem ser expostos mesmo se o seu próprio código for seguro.
Two serious NGINX flaws, CVE-2026-123633 and CVE-2026-123007, were disclosed on 18 November 2026.
Both require NGINX to accept HTTP/2 connections, and exposure depends on version and configuration.
Wiz demonstrated code execution for CVE-2026-123007 on NGINX serving static files alone; affected Open Source versions range from 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8.
Versions 1.30.7 and 1.31.9 fix both flaws.
Use in attacks a…
We've just pushed a mitigation for the Nginx RCE vulnerability published an hour ago (CVE-2026-123007 and CVE-2026-123633). We recommend upgrading your servers as soon as possible.
NGINX shipped 1.31.9 (mainline) and 1.30.7 (stable) today with fixes for 10 CVEs. The two to care about: CVE-2026-123633 and CVE-2026-123007, HTTP/2 memory bugs that Wiz says allow unauthenticated remote code execution (CVSS 4.0 9.2). One reaches back to 1.9.5 from 2015. Exploitation needs HTTP/2 on. No in-the-wild attacks reported so far. Upgrade, or turn off HTTP/2 until you can.
NGINX HTTP/2 RCE Vulnerabilities (CVE-2026-123633 and CVE-2026-123007): Technical Analysis and How to Patch
Critical NGINX HTTP/2 vulnerability pair (CVE-2026-123633, CVE-2026-123007) allows unauthenticated RCE. How they work, affected versions, and how to patchhttps://thecybersecguru.com/exploits/nginx-http2-vulnerability-cve-2026-123633-123007/
> The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated Critical, with a CVSS 4.0 score of 9.2. The flaws are in NGINX itself. Websites and APIs can be exposed even when their own application code is secure. Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. Additional conditions are described below. CVE-2026-123007 affects versions dating back to NGINX 1.9.5 in 2015.
#infosec #rce #vulnerability
https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
Bluesky
Overview
Description
Statistics
- 9 Posts
- 4 Interactions
Fediverse
U.S. CISA adds Perforce Puppet Enterprise flaw to its Known Exploited Vulnerabilities catalog
Hackers Exploiting Critical Puppet RCE Flaw Affecting Enterprise Management Servers
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has added a critical flaw in Perforce Puppet to its Known Exploited Vulnerabilities catalog, citing reports of active exploitation. The vulnerability, tracked as CVE-2026-115731 and rated 9.4, affects servers of the enterprise infrastructure-as-code and configuration management platform. https://thehackernews.com/2026/11/hackers-exploiting-critical-puppet-rce.html
(CISA TS+SOC) The Cyber Mind TSUITE Brief: CVE-2026-115731 – Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
A critical deserialization flaw in Perforce Puppet Enterprise (CVE-2026-115731) allows arbitrary code execution via crafted rich-data reports....
(CISA CS-MAN) The Cyber Mind CSUITE Brief: CVE-2026-115731 – Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
Executive leadership must immediately evaluate enterprise exposure to CVE-2026-115731, a critical deserialization vulnerability in Perforce Puppet Enterprise....
📰 Critical RCE Flaw in Perforce Puppet (CVE-2026-115731) Actively Exploited
🚨 CRITICAL & ACTIVELY EXPLOITED: RCE vulnerability CVE-2026-115731 (CVSS 9.4) in Perforce Puppet allows full infrastructure takeover. Any client with a signed cert can execute code on the server. Patch immediately! #Puppet #RCE #Vulnerability #DevOps
🚨 Hackers actively exploiting critical Perforce Puppet flaw to hijack enterprise management servers; CVE-2026-115731
CISA has confirmed active exploitation of a critical vulnerability in Perforce Puppet, a widely used enterprise configuration management platform.
The flaw, tracked as CVE-2026-115731 (CVSS 9.4), allows attackers possessing a Puppet CA-signed certificate to remotely execute malicious code on vulnerable servers.
Successful exploitation could expose certificate-signing keys, allowing attackers to impersonate trusted systems and potentially push malicious configurations across entire corporate networks.
CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on November 17. Perforce has released security updates for Puppet Enterprise and Puppet Core, urging administrators to patch immediately.
Bluesky
Overview
- Apache Software Foundation
- Apache HTTP Server
Description
Statistics
- 4 Posts
- 1 Interaction
Fediverse
Singapore CSA warns of active attacks and public PoC code for CVE-2026-119618, a critical Apache RCE flaw in mod_http2. Update to 2.4.71 immediately.
#Apache #ApacheHTTPServer #CVE2026119618 #mod_http2 #RCE #PoC #ExploitedInTheWild #Cybersecurity
Apache HTTP Server: RCE-Lücke CVE-2026-119618 wird aktiv ausgenutzt - Für die Schwachstelle CVE-2026-119618 im Apache HTTP Server liegen öffentliche Exploit-Details und ein Proof-of-Concept vor. Singapurs Cybersicherheitsbehörde meldet Angriffe in der Praxis. Betroffen sind Installationen mit aktiviertem mod_http2. Administratoren sollten auf Version 2.4.71 aktualisieren oder HTTP/2 deaktivieren.
HTTPd (CVE-2026-119618): Detecting heap corruption and RCE in Apache HTTP Server mod_http2 | Sysdig #devopsish https://webflow.sysdig.com/blog/httpd-cve-2026-119618-detecting-heap-corruption-and-rce-in-apache-http-server-mod-http2
Overview
Description
Statistics
- 2 Posts
- 24 Interactions
Fediverse
Take CVE-2026-99288, for example. If you raced to deploy Debian's 6.1.192-1 kernel, you accidentally deployed an unrelated bug that might kill your system: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1154101
We're all basically crossing our fingers, hoping that whatever upstream provides to fix today's vulnerability doesn't break anything else. At this tempo, nobody has time to actually validate updates with long bake-in times & canary deployments.
Or rather, you have to choose between remaining vulnerable & reliability.
Karen IT Security Response Center (@ksrc) Advisory
Advisory ID: KSRC-2026-11171
A #critical race condition in the Linux kernel’s TCP networking #code allows a #remote, unauthenticated #attacker to trigger a kernel panic and crash the host. Tracked as CVE-2026-99288 and commonly referred to as #NoisyTCP, the flaw was discovered and reported by security researcher Hyunwoo Kim (@v4bel).
The #vulnerability has existed since Linux 4.4 (introduced in October 2015) and affects virtually all major #Linux distributions until patched. Red Hat rates it as Important with a CVSS v3.1 score of 7.5. Confirmed impact is remote denial of service; reliable remote code execution has not been demonstrated.
Overview
Description
Statistics
- 5 Posts
Fediverse
CVE-2026-99312 Explained: How a KVM Bug Let a VM Read Its Host’s Memory
A technical breakdown of CVE-2026-99312, the AMD KVM nested virtualization bug that let a guest VM read and write host physical memoryhttps://thecybersecguru.com/exploits/cve-2026-99312-kvm-nested-svm-guest-to-host-escape/
Overview
Description
Statistics
- 2 Posts
- 1 Interaction
Fediverse
🚨 New attack bypasses Windows Hello and BitLocker security, cracking PINs in hours instead of months
Security researchers at TU Berlin have demonstrated a hardware attack dubbed "Hello Again" that bypasses TPM lockout protections, allowing attackers with physical access to repeatedly guess Windows Hello and BitLocker PINs.
The attack manipulates security counters stored in motherboard flash memory, reducing the estimated worst-case time to crack a 4-digit Windows Hello PIN from 69 days to just 40 hours. A 6-digit BitLocker PIN could be cracked in approximately 20 days instead of 19 years.
The vulnerabilities affect certain AMD and Intel-based systems. AMD has acknowledged one flaw as CVE-2026-43613 and is preparing firmware updates.
Researchers recommend longer PINs to reduce the risk.
Source: https://arxiv.org/abs/2611.18126
Researchers at Technische Universität Berlin have demonstrated a method to bypass PIN locks on Windows Hello and BitLocker by physically accessing the device and targeting specific memory chips paired with AMD processors.
The technique allows attackers to reset the failed attempt counter, drastically speeding up PIN discovery.
AMD has confirmed a firmware issue (CVE-2026-43613) with patches planned through early 2027.
Overview
Description
Statistics
- 5 Posts
- 1 Interaction
Fediverse
CW: PHP2Shell — kritikus RCE (CVE-2026-109618, CVE-2026-109619). A PHP memóriakezelésében és elavult jegyzetekben lévő hibák mod_php alatt távolról, bejelentkezés nélkül kódfuttatást és memóriakivonást tesznek lehetővé. Javítások kiadva 8.2–8.5-hoz; régebbi ágakhoz csak forrásjavítás. Frissíts, indítsd újra a PHP-folyamatokat, és ellenőrizd a kompromittáltság jeleit. Részletek: https://linuxmint.hu/hir/2026/11/php2shell-avagy-elephpant-a-porcelanboltban
#PHP #RCE #Cybersecurity #OpenSource
🔒 New CSAF advisory published
VDE-2026-144
Phoenix Contact: PHP2Shell in FL SWITCH, FL NAT and FL WLAN devices
CVE-2026-109618, CVE-2026-109619
Two vulnerabilities have been identified in the PHP component used in FL SWITCH, FL NAT, and FL WLAN devices. The vulnerabilities relate to improper memory handling i…
HTML: https://certvde.com/en/advisories/VDE-2026-144
CSAF JSON: https://phoenixcontact.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2026-144.json
🔄 CSAF advisory updated (version 2.0.0)
VDE-2026-132
WAGO: Multiple Devices affected by PHP2Shell
CVE-2026-109618, CVE-2026-109619
Changes: Added affected firmware versions and IPK remediation information.
HTML: https://certvde.com/en/advisories/VDE-2026-132
CSAF JSON: https://wago.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2026-132.json
Bluesky
Overview
Description
Statistics
- 5 Posts
- 1 Interaction
Fediverse
CW: PHP2Shell — kritikus RCE (CVE-2026-109618, CVE-2026-109619). A PHP memóriakezelésében és elavult jegyzetekben lévő hibák mod_php alatt távolról, bejelentkezés nélkül kódfuttatást és memóriakivonást tesznek lehetővé. Javítások kiadva 8.2–8.5-hoz; régebbi ágakhoz csak forrásjavítás. Frissíts, indítsd újra a PHP-folyamatokat, és ellenőrizd a kompromittáltság jeleit. Részletek: https://linuxmint.hu/hir/2026/11/php2shell-avagy-elephpant-a-porcelanboltban
#PHP #RCE #Cybersecurity #OpenSource
🔒 New CSAF advisory published
VDE-2026-144
Phoenix Contact: PHP2Shell in FL SWITCH, FL NAT and FL WLAN devices
CVE-2026-109618, CVE-2026-109619
Two vulnerabilities have been identified in the PHP component used in FL SWITCH, FL NAT, and FL WLAN devices. The vulnerabilities relate to improper memory handling i…
HTML: https://certvde.com/en/advisories/VDE-2026-144
CSAF JSON: https://phoenixcontact.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2026-144.json
🔄 CSAF advisory updated (version 2.0.0)
VDE-2026-132
WAGO: Multiple Devices affected by PHP2Shell
CVE-2026-109618, CVE-2026-109619
Changes: Added affected firmware versions and IPK remediation information.
HTML: https://certvde.com/en/advisories/VDE-2026-132
CSAF JSON: https://wago.csaf-tp.certvde.com/.well-known/csaf/white/2026/vde-2026-132.json