Overview
- Oracle Corporation
- Oracle Java SE
Description
Statistics
- 93 Posts
- 159 Interactions
Fediverse
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
Hinweise von Keycloak Team
https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938 #java4Shell
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.!
⚠️📢 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/
Security advisory for #Openfire admins: two unrelated issues, neither in Openfire's own code, both needing your attention.
Java4Shell (CVE-2026-114938) is a bug in OpenJDK's Base64 decoder. Openfire decodes Base64 during authentication, so treat vulnerable installs as exposed. Check which Java you run and apply your vendor's November update.
The compromised eMudhra/emSign CAs may still be in your trust store. Remove emSign ECC Root CA - G3.
https://discourse.igniterealtime.org/t/security-advisory-java4shell-and-emudhra-certificates/96655
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:
Everyone running Keycloak, you might need to add an env variable to fix java2shell: https://www.keycloak.org/2026/11/java4shell-vulnerability-cve-2026-114938
I got lucky, my instance is running on one of my Pis right now.
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.
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.
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/
CVE-2026-114938 : Une faille du décodeur Base64 d’OpenJDK permet l’exécution de code à distance sur certains processeurs x86-64
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
Are people actually seeing exploitation attempts, blocked or otherwise, for #Java4Shell / #CVE2026114938?
The report flags Java4Shell (CVE-2026-114938), a potentially critical Java RCE, as Oracle’s 11 Java fixes leave one question: is it covered? Administrators are urged to patch promptly, prioritizing internet-facing systems. ⚠️🔐 #Java #Cybersecurity www.heise.de/en/news/Java4Shell-Dangerous-Java-vulnerability-11528504.html | Published: Nov. 17, 2026
Patch Java4Shell!
Calif researcher Quang Luong said they discovered CVE-2026-114938 while “developing a 0-click exploit on a certain phone vendor.”
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/
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.
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
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
Once you’re done flipping your desk for the 3rd time this week, get your hands on this free #Java4Shell (CVE-2026-114938) scanner. 🎯
It reads the Java version your Solr, Elasticsearch, Spring Boot, Quarkus, or Jolokia endpoints already expose, and tells you if it lands in an affected range, in a PDF report you can hand to whoever owns the patch. No payloads, no login, no email.
Java4Shell is pickier than most critical CVEs: it needs an affected JVM, the right CPU, and an exploit built for each target. Fewer hosts qualify, but finding them is the hard part.
What it can’t see (and nothing remote can): your CPU and JVM flags. Our deep dive shows you where to look on the host.
Scan for free: https://pentest-tools.com/network-vulnerability-scanning/java4shell-scanner-cve-2026-114938
Deep dive: https://pentest-tools.com/blog/java4shell-cve-2026-114938
Java4shell CVE-2026-114938 https://thehackernews.com/2026/11/java4shell-cve-2026-114938-enables-pre.html?m=1
RE: https://infosec.exchange/@censys/117634278507700588
🚨 Rapid Response Update: New developments surrounding Java4Shell (CVE-2026-114938).
Censys ARC has updated its advisory with a detailed list of affected software, exploit reports, and updated mitigation guidance, including CISA-recommended actions to update affected Java installations and restart every JVM.
https://censys.com/advisory/cve-2026-114938/
#Java4Shell #OpenJDK #JavaSecurity #CVE2026114938 #RemoteCodeExecution #VulnerabilityManagement #CyberSecurity #ThreatIntelligence
Java4Shell Remove Code Execution (RCE) Vulnerability (CVE-2026-114938) advisory for #elasticsearch: https://discuss.elastic.co/t/java4shell-remove-code-execution-rce-vulnerability-cve-2026-114938/391703
everyone stay safe out there #hugops
A significant supply-chain cyberattack via Optimizely impacted over 178 organizations, including CNN, BBC, and Zoom, allowing for cryptocurrency theft and data skimming (Nov 17). CISA has issued an urgent advisory for organizations to immediately patch the critical "Java4Shell" vulnerability (CVE-2026-114938), which enables remote code execution. Geopolitically, President Trump arrived in China for key trilateral discussions with Presidents Xi Jinping and Vladimir Putin (Nov 18). The FBI also cautioned about rising threats from AI-driven cyberattacks.
Red Hat OpenJDK 17 for Windows patched (CVE-2026-114938) – CRITICAL update resolves RCE & Kerberos flaws. Upgrade to 17.0.21.1 urgently. No exploits seen yet. Details: https://radar.offseq.com/threat/red-hat-security-advisory-openjdk-170211-security-update-for-windows-builds-05972bb47b6d059b #OffSeq #RedHat #OpenJDK #Vulnerability #InfoSec
Bluesky
Overview
Description
Statistics
- 68 Posts
- 228 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)
Pretty nasty nginx RCE just dropped.
https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
Here's a quick nondestructive/work-approved checker: https://gist.github.com/SiteRelEnby/eddfde961ee1d39c14076a53714762b2
Here we go again. We have the latest on the new Nginx vulnerabilities. TL;DR: most folks don't have to panic, and turning off HTTP/2 is a reasonable mitigation until patches are available.
https://ifin.network/t/cve-2026-123633-cve-2026-123007-rce-paths-in-nginx-via-http-2/1001
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):
Just in case, we dropped http2 from #mementomori for time being until nginx is fixed. Tell us if there are problems.
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?
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
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
🚨 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/
CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED)
Rapid7 and F5 have disclosed CVE-2026-123007, a critical integer underflow in NGINX’s HTTP/2 flow-control handling that can let an unauthenticated client corrupt memory and execute code with the NGINX worker process’s permissions; Rapid7 demonstrated remote code execution against NGINX 1.31.8. Exploitation is bandwidth-hungry — roughly 128 GB of HTTP/2 traffic — which limits practical internet exploitation, and a fix is available, so upgrading is the priority. https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed
POC CVE-2026-123007 https://github.com/sfewer-r7/CVE-2026-123007 integer underflow in NGINX HTTP/2.
Karen IT Security Response Center (@ksrc) Advisory
Advisory ID: KSRC-2026-11182
A #critical unauthenticated #remote code execution #vulnerability has been disclosed in NGINX’s HTTP/2 implementation. Tracked as CVE-2026-123007 and commonly referred to as nginx2root or NGINX2Shell, the flaw allows an attacker to execute arbitrary code on vulnerable #NGINX servers without #authentication.
The vulnerability carries a CVSS v4.0 score of 9.2 (Critical) and affects a very wide range of NGINX versions dating back to 2015. A public proof-of-concept exploit is already available.
Memory corruption in HTTP/2 flow control
Severity: major
Advisory
CVE-2026-123007
Not vulnerable: 1.31.9+, 1.30.7+
Vulnerable: 1.9.5-1.31.8
You think:
* Just Linux TCP stack
* Just Node
* Just PHP
* Just Java
* Just ... Nginx
And you end up with a question: what will GLM 5.5 bring? The authors already said they will scale and increase affordability.
Here is the clue to connect the dots: no one invested into secure coding. Not F5. Not Oracle. Not PHP. Not Linux. Not you, not your boss. Not Microsoft, not Amazon. 0.
Given that companies / software makers play the layoff wave game, what makes you think 2027 will get better?
#nginx #infosec
#patch #glm #thinkahead
🚨 #NGINX: A 10-year-old NGINX HTTP/2 vulnerability (CVE-2026-123007) enables unauthenticated attackers to execute code on vulnerable servers.
PoC is public. Patch NOW: 1.31.9 or 1.30.7.
#AppSec #CyberSecurity
#NGINX2Shell
#nginx2root
👇
https://thehackernews.com/2026/11/10-year-old-nginx-http2-flaw-lets.html
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)
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.
⚠️ 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/
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.
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.
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.
jesus fucking christ
☠️ 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…
Passbolt 5.18.0-2 Debian and RPM packages include a default Nginx configuration that sets http2 off;. This mitigates the two HTTP/2 vulnerabilities affecting self-hosted Passbolt installations using Nginx: CVE-2026-123007 and CVE-2026-123633.
If you have a customized Nginx configuration, verify that HTTP/2 is disabled after upgrading. We plan to restore the default HTTP/2 setting in a future release once patched Nginx packages are available across our supported operating systems.
The fun of operating a server on the public internet ...
https://www.cve.org/CVERecord?id=CVE-2026-123633
https://www.cve.org/CVERecord?id=CVE-2026-123007
TLDR: Patch your nginx or disable http2 - i did the latter...
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
🚨 Five vulnerabilities in nginx, nicknamed NGINX2Root, were disclosed by nginx today: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-113425, and CVE-2026-121810.
AlmaLinux 8, 9, and 10 all ship affected nginx versions.
Due to the severity, patches went straight to the production repositories. Update as soon as you can!
More information: https://almalinux.org/blog/2026-11-18-nginx2root/
Bluesky
Overview
- F5
- NGINX Open Source
Description
Statistics
- 44 Posts
- 197 Interactions
Fediverse
Here we go again. We have the latest on the new Nginx vulnerabilities. TL;DR: most folks don't have to panic, and turning off HTTP/2 is a reasonable mitigation until patches are available.
https://ifin.network/t/cve-2026-123633-cve-2026-123007-rce-paths-in-nginx-via-http-2/1001
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):
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)
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.
⚠️ 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/
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.
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.
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.
jesus fucking christ
☠️ 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…
Passbolt 5.18.0-2 Debian and RPM packages include a default Nginx configuration that sets http2 off;. This mitigates the two HTTP/2 vulnerabilities affecting self-hosted Passbolt installations using Nginx: CVE-2026-123007 and CVE-2026-123633.
If you have a customized Nginx configuration, verify that HTTP/2 is disabled after upgrading. We plan to restore the default HTTP/2 setting in a future release once patched Nginx packages are available across our supported operating systems.
The fun of operating a server on the public internet ...
https://www.cve.org/CVERecord?id=CVE-2026-123633
https://www.cve.org/CVERecord?id=CVE-2026-123007
TLDR: Patch your nginx or disable http2 - i did the latter...
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
🚨 Five vulnerabilities in nginx, nicknamed NGINX2Root, were disclosed by nginx today: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-113425, and CVE-2026-121810.
AlmaLinux 8, 9, and 10 all ship affected nginx versions.
Due to the severity, patches went straight to the production repositories. Update as soon as you can!
More information: https://almalinux.org/blog/2026-11-18-nginx2root/
Bluesky
Overview
- Apache Software Foundation
- Apache HTTP Server
Description
Statistics
- 7 Posts
- 15 Interactions
Fediverse
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
Cyber Security Agency of Singapore (CSA) is reporting active exploitation of CVE-2026-119618 (8.1 high) Apache HTTP Server: mod_http2: heap corruption and RCE in assign_headers https://www.csa.gov.sg/alerts-and-advisories/alerts/al-2026-164/
No other open source article has any exploitation evidence or even scanning for this vulnerability. I'm skeptical because I don't get tips like this from CSA Singapore.
Apache admins face a critical HTTP/2 flaw (CVE-2026-119618) that could enable remote code execution. Upgrade to 2.4.71 or disable HTTP/2 until patched. 🔒🛠️ #Apache #Cybersecurity www.aikido.dev/blog/cve-2026-119618-apache-http-server-rce | Nov. 13, 2026 #oldnews
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
Excuse a bit of a rant, aimed in no particular direction.
I received an email from the NCSC via Netcraft last week, warning me that my Nextcloud instance contained the Apache mod_http2 vulnerability (CVE-2026-119618). They also sent the warning to Hetzner who sent me a nastygram about my responsibilities to check it out.
Here's the problem: I'm running Nextcloud in a Docker container, and the maintainers aren't in any rush to update apache to 2.4.71 any time soon.
1/3
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.
Overview
Description
Statistics
- 10 Posts
- 3 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
Description
Statistics
- 4 Posts
- 30 Interactions
Fediverse
WTF ANOTHER CRITICAL PHP VULN?! https://www.aikido.dev/blog/php-security-release-19-november-2026-cve-2026-115560
A critical PHP security release lands November 19 and is expected to fix CVE-2026-115560, a session upload progress RCE. Conditions and mitigation.
#PHP #CVE2026115560 #RCE #PHP2Shell #PatchNow #CyberSecurity #InfoSec
The PHP security team has scheduled critical updates for all supported versions to be released on November 19, 2026, between 14:00 and 14:30 UTC.
The patches address multiple vulnerabilities, including CVE-2026-115560 which involves session upload progress.
As a temporary mitigation, PHP suggests disabling session upload progress.
Please note that restarting PHP workers is required after applying these patches to ensure the fixes t…
https://en.hacks.gr/krisimi-enimerosi-asfaleias-gia-tin-php-erchetai-stis-19-noemvrioy/
Overview
Description
Statistics
- 5 Posts
- 2 Interactions
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
- Apache Software Foundation
- Apache Roller
Description
Statistics
- 4 Posts
- 2 Interactions
Fediverse
Apache warns of Roller RCE vulnerability exploited in attacks
Apache has released Roller 6.1.6 to fix a critical deserialization flaw (CVE-2026-129448) that it says is being actively exploited: the XML-RPC endpoint in Roller 4.0.0 through 6.1.4 deserializes vendor extension types before authenticating the requester, allowing unauthenticated remote code execution. Apache has shared no details yet on who is behind the attacks or how many servers are compromised; admins who cannot upgrade immediately can mitigate by disabling extension types in web.xml and removing the XML-RPC servlet mapping. https://www.bleepingcomputer.com/news/security/apache-warns-of-roller-rce-vulnerability-exploited-in-attacks/
Apache Roller RCE Flaw CVE-2026-129448 Under Active Attack
🚨 Hackers actively exploiting critical Apache Roller flaw to take control of servers without authentication; CVE-2026-129448
The Apache Software Foundation has confirmed active exploitation of a critical vulnerability in its Java-based Roller blogging platform, allowing unauthenticated attackers to remotely execute arbitrary code on vulnerable servers.
The flaw involves unsafe deserialization in the XML-RPC endpoint, which processes malicious requests before verifying authentication.
Versions 4.0.0 through 6.1.5 are affected, with version 6.1.5 tracked separately as CVE-2026-82384.
Apache has released version 6.1.6 to address the vulnerability and urges administrators to upgrade immediately. The attackers' identities and number of compromised servers remain unknown.
Source: https://lists.apache.org/thread/lnz4s26tv6hdo03wngtdbpfj4hg4gtds
Apache Roller zero-day CVE-2026-129448 (9.8 critical) Unauthenticated deserialization in the XML-RPC endpoint
This is the same vulnerability as CVE-2026-82384, which listed only Apache Roller 6.1.5 as affected. This issue is being actively exploited.
https://lists.apache.org/thread/lnz4s26tv6hdo03wngtdbpfj4hg4gtds
Overview
Description
Statistics
- 4 Posts
- 1 Interaction
Fediverse
🚨 NEW on CISA KEV — exploited in the wild
🛡 BerriAI LiteLLM
BerriAI LiteLLM Unprotected Alternate Channel Vulnerability
CVE: CVE-2026-40217 · patch by 2026-12-02
📈 EPSS 17.0% exploitation probability
BerriAI LiteLLM contains an unprotected alternate channel vulnerability that could allow remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
🔗 https://ninjasignal.ninja/intel/cve/CVE-2026-40217
#cybersecurity #KEV #CVE #infosec
CISA adds 4 Exploited Flaws to its KEV catalog: CVE-2024-10441, CVE-2026-40217, CVE-2026-90436, and CVE-2026-90817. Review federal patch deadlines now.
#CISA #CISAKEV #Synology #LiteLLM #ApacheAxis #REDCap #CVE202410441 #CVE202640217 #CVE202690436 #Cybersecurity
The first half of #4EverAble2Shell CVE-2026-90436 was added to CISA's KEV Catalog today: https://www.cisa.gov/news-events/alerts/2026/11/18/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CVE-2024-10441 (9.8 critical) Synology DiskStation Manager (DSM) Improper Encoding or Escaping of Output Vulnerability
- CVE-2026-40217 (8.8 high) BerriAI LiteLLM Unprotected Alternate Channel Vulnerability
- CVE-2026-90436 (9.8 critical) Apache Axis Unsafe Reflection Vulnerability
- CVE-2026-90817 (9.8 critical) Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability
Overview
Description
Statistics
- 4 Posts
- 1 Interaction
Fediverse
CISA adds 4 Exploited Flaws to its KEV catalog: CVE-2024-10441, CVE-2026-40217, CVE-2026-90436, and CVE-2026-90817. Review federal patch deadlines now.
#CISA #CISAKEV #Synology #LiteLLM #ApacheAxis #REDCap #CVE202410441 #CVE202640217 #CVE202690436 #Cybersecurity
The first half of #4EverAble2Shell CVE-2026-90436 was added to CISA's KEV Catalog today: https://www.cisa.gov/news-events/alerts/2026/11/18/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CVE-2024-10441 (9.8 critical) Synology DiskStation Manager (DSM) Improper Encoding or Escaping of Output Vulnerability
- CVE-2026-40217 (8.8 high) BerriAI LiteLLM Unprotected Alternate Channel Vulnerability
- CVE-2026-90436 (9.8 critical) Apache Axis Unsafe Reflection Vulnerability
- CVE-2026-90817 (9.8 critical) Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability