[{"data":1,"prerenderedAt":1691},["ShallowReactive",2],{"post-en-nginx-http2-lucken-codeausfuhrung-ohne-anmeldung":3,"related-en-nginx-http2-lucken-codeausfuhrung-ohne-anmeldung":446},{"id":4,"title":5,"author":6,"body":7,"category":414,"date":415,"description":416,"draft":417,"extension":418,"faq":419,"image":431,"imageAlt":432,"lang":433,"legacyUrl":434,"meta":435,"navigation":436,"path":437,"readingTime":438,"seo":439,"sitemap":440,"stem":441,"tags":442,"translation":444,"updated":434,"__hash__":445},"insightsEn\u002Fen\u002Finsights\u002Fnginx-http2-lucken-codeausfuhrung-ohne-anmeldung.md","nginx and HTTP\u002F2: two flaws allow code execution without login","blacklens.io Team",{"type":8,"value":9,"toc":402},"minimark",[10,14,19,59,84,88,91,155,164,173,177,187,194,198,205,212,216,219,265,272,276,279,364,368,392],[11,12,13],"p",{},"Since 18 November 2026, nginx 1.30.7 and 1.31.9 are available, and with them fixes for two flaws that let attackers run code on an nginx server without logging in. The older one has been in every nginx version that speaks HTTP\u002F2 since 2015; the only precondition is that HTTP\u002F2 is switched on. A proof of concept went public on the day of disclosure. According to Rapid7, an attack with it does, however, need around 128 gigabytes of traffic in under an hour.",[15,16,18],"h2",{"id":17},"what-are-cve-2026-123007-and-cve-2026-123633","What are CVE-2026-123007 and CVE-2026-123633?",[11,20,21,25,26,29,30,33,34,41,42,46,47,49,50,55,56,58],{},[22,23,24],"code",{},"CVE-2026-123007"," and ",[22,27,28],{},"CVE-2026-123633"," are two memory-safety flaws in the nginx HTTP\u002F2 module ",[22,31,32],{},"ngx_http_v2_module",", fixed on 18 November 2026 in nginx 1.30.7 (stable) and 1.31.9 (mainline) and in NGINX Plus 37.0.8.1 and 37.3.0.1. F5, which makes nginx and issued the ",[35,36,40],"a",{"href":37,"rel":38},"https:\u002F\u002Fwww.cve.org\u002FCVERecord?id=CVE-2026-123007",[39],"nofollow","CVE records",", rates both at ",[35,43,45],{"href":44},"\u002Fen\u002Fwissen\u002Fcvss","CVSS"," 9.2 under version 4.0 and 8.1 under version 3.1. The nginx project rates ",[22,48,24],{}," as \"major\" on its ",[35,51,54],{"href":52,"rel":53},"https:\u002F\u002Fnginx.org\u002Fen\u002Fsecurity_advisories.html",[39],"security page",", and ",[22,57,28],{}," only as \"medium\".",[11,60,61,62,67,68,25,73,78,79,83],{},"Several teams found the bugs independently; the CVE records credit Wiz Research, Rapid7, Xint, Metnir and Ikotas Labs. ",[35,63,66],{"href":64,"rel":65},"https:\u002F\u002Fwww.wiz.io\u002Fblog\u002Fnginx-http2-rce-vulnerabilities",[39],"Wiz",", ",[35,69,72],{"href":70,"rel":71},"https:\u002F\u002Fwww.rapid7.com\u002Fblog\u002Fpost\u002Fve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed\u002F",[39],"Rapid7",[35,74,77],{"href":75,"rel":76},"https:\u002F\u002Fxint.io\u002Fblog\u002Fnginx2root-remote-code-execution",[39],"Xint"," published their own analyses the same day. Xint groups the two flaws with three other nginx bugs and a Linux kernel bug under the name \"nginx2root\". The same release fixes ten CVEs, including use-after-free bugs in HTTP\u002F3, the DNS resolver and the mail proxy. That brings nginx.org to 36 flaws with a 2026 CVE number, against two from 2025. According to Xint, a fully automated scan found four of its five nginx flaws, the pattern described in our ",[35,80,82],{"href":81},"\u002Fen\u002Finsights\u002Fclaude-mythos-wenn-schwachstellen-schneller-kommen-als-patches","post on Claude Mythos",".",[15,85,87],{"id":86},"two-bugs-two-sets-of-conditions","Two bugs, two sets of conditions",[11,89,90],{},"Both flaws require HTTP\u002F2 to be enabled. In nginx that is not a default but a line in the configuration. Beyond that, they differ considerably:",[92,93,94,107],"table",{},[95,96,97],"thead",{},[98,99,100,103,105],"tr",{},[101,102],"th",{},[101,104,24],{},[101,106,28],{},[108,109,110,122,133,144],"tbody",{},[98,111,112,116,119],{},[113,114,115],"td",{},"Bug",[113,117,118],{},"Flow-control calculation error",[113,120,121],{},"Use-after-free",[98,123,124,127,130],{},[113,125,126],{},"Since",[113,128,129],{},"1.9.5 (2015)",[113,131,132],{},"1.19.7 (2021)",[98,134,135,138,141],{},[113,136,137],{},"Also required",[113,139,140],{},"–",[113,142,143],{},"Proxying to a backend, scarce connections",[98,145,146,149,152],{},[113,147,148],{},"Public exploit",[113,150,151],{},"yes (Rapid7)",[113,153,154],{},"no",[11,156,157,159,160,163],{},[22,158,24],{}," sits in HTTP\u002F2 flow control. A client uses ",[22,161,162],{},"WINDOW_UPDATE"," frames to tell the server how much data it can accept, and nginx keeps a send window per connection that the standard caps at 2³¹−1 bytes. When the client cancels a stream, nginx credits the unsent data back to the window without checking that cap. The next check then miscalculates: nginx takes on a negative length and, when sending over TLS, copies far past the end of a buffer. According to Wiz, a server delivering ordinary static files is enough, with no backend and no extra module. Version 1.9.5 is the release in which nginx introduced HTTP\u002F2.",[11,165,166,168,169,172],{},[22,167,28],{}," concerns connection management. An HTTP\u002F2 connection without active streams sits on a list of reusable connections, which nginx closes when free ",[22,170,171],{},"worker_connections"," run low. If an attacker sends only half of a header frame, the connection stays on that list even though a request is being built on it. When nginx then opens a connection to the backend for that request and frees slots in the process, it releases the memory of its own connection and carries on using it. That is a use-after-free: access to memory that has already been released. An attacker does not have to wait for slots to run low. According to Xint, its exploit creates that pressure itself with additional connections.",[15,174,176],{"id":175},"how-realistic-an-attack-is","How realistic an attack is",[11,178,179,180,182,183,83],{},"Code execution has been demonstrated in the lab for both flaws; as of 18 November, no attacks in the wild are known. Wiz, Rapid7 and Xint each built their own exploits, and Xint says it tested its exploit against servers on AWS, Google Cloud and Azure. Only Rapid7 has published a proof of concept, for ",[22,181,24],{},", on GitHub on 18 November. In the CVE record, CISA rates exploitation of that flaw as \"none\", and neither flaw is in the ",[35,184,186],{"href":185},"\u002Fen\u002Fwissen\u002Fcisa-kev","KEV catalogue",[11,188,189,190,193],{},"The effort is high. F5 describes a crash of the worker process as the typical outcome; an attacker could execute code if ASLR is disabled or bypassed. That is exactly what the three teams did. Wiz still calls the flaws hard to exploit remotely, because an attacker has to leak memory addresses, shape the heap precisely and cope with different builds and configurations. Rapid7 needs around 128 gigabytes of HTTP\u002F2 data for code execution. At 10 Gbit\u002Fs that takes about two minutes, at 1 Gbit\u002Fs 17 minutes. Below roughly 300 Mbit\u002Fs the attack fails, because nginx closes a connection after one hour by default. Rapid7's exploit also depends on a specific ",[22,191,192],{},"memcpy"," variant in glibc on x86-64; according to Rapid7, no other routes are currently known.",[15,195,197],{"id":196},"from-worker-process-to-root","From worker process to root",[11,199,200,201,204],{},"Injected code runs with the rights of the nginx worker process, usually an unprivileged user such as ",[22,202,203],{},"www-data",". That is enough to read the traffic this worker handles and to reach systems the server can see on the internal network.",[11,206,207,208,211],{},"Xint goes one step further. Combined with a still unpatched bug in the SCTP code of the Linux kernel, the team says it gained root on the host, including from inside a Docker container. The kernel bug has no CVE number and no patch yet. Xint is withholding the details until then and recommends blocking the ",[22,209,210],{},"sctp"," kernel module wherever SCTP is not needed. A container is therefore not a boundary to rely on with these flaws.",[15,213,215],{"id":214},"where-the-fix-has-not-arrived-yet","Where the fix has not arrived yet",[11,217,218],{},"The update on nginx.org does not reach many servers directly, because they get nginx from package repositories, container images or third-party products. Those follow their own schedules and their own version numbers:",[220,221,222,230,236,259],"ul",{},[223,224,225,229],"li",{},[226,227,228],"strong",{},"Distributions:"," Debian 13 ships nginx 1.26.3, Debian 12 nginx 1.22.1 and Ubuntu 24.04 nginx 1.24.0, all in the affected range. Fixes arrive there as backports under the old version number. In the late afternoon of 18 November, the Debian and Ubuntu security trackers did not yet list the two CVEs.",[223,231,232,235],{},[226,233,234],{},"Container images:"," The official nginx image on Docker Hub was still on 1.31.8 at around 17:00 CET on 18 November. Images built on it need a rebuild once it is updated.",[223,237,238,241,242,245,246,249,250,253,254,258],{},[226,239,240],{},"Kubernetes:"," The ingress-nginx controller has been archived since March 2026. Its last release, ",[22,243,244],{},"controller-v1.15.1",", is built on nginx 1.27.1 and enables HTTP\u002F2 by default (option ",[22,247,248],{},"use-http2",", default ",[22,251,252],{},"true","). No fix will come from the project. That is one more reason for the migration our ",[35,255,257],{"href":256},"\u002Fen\u002Finsights\u002Ftrust-no-origin-cors-mirage-in-azure-ingress","post on the CORS flaw in Azure's ingress"," already recommended.",[223,260,261,264],{},[226,262,263],{},"NGINX Plus and forks:"," F5 names fixed versions only for NGINX Plus 37. The CVE record lists the R releases from R33 onwards as affected, with no fixed version; older ones were not evaluated by F5. The fork Angie did not yet list the two CVEs in its security advisories on 18 November. For forks and appliances, the respective vendor's notice is what counts.",[11,266,267,268,271],{},"Version numbers mislead in both directions. A patched Debian package still reports 1.26.3, and a server with ",[22,269,270],{},"server_tokens off"," does not reveal its version at all.",[15,273,275],{"id":274},"what-to-do-now","What to do now",[11,277,278],{},"The update comes first; disabling HTTP\u002F2 bridges the time until it is installed:",[220,280,281,291,313,331,337,354],{},[223,282,283,286,287,290],{},[226,284,285],{},"Update:"," nginx 1.30.7 or 1.31.9, NGINX Plus 37.0.8.1 or 37.3.0.1, and for distributions the package's security update as soon as it is out. Then restart the service; ",[22,288,289],{},"nginx -s reload"," only reloads the configuration, not the new binary.",[223,292,293,296,297,300,301,304,305,308,309,312],{},[226,294,295],{},"Disable HTTP\u002F2 where the update has to wait:"," from nginx 1.25.1, set ",[22,298,299],{},"http2 off;"," in every affected ",[22,302,303],{},"server"," block and remove the ",[22,306,307],{},"http2"," parameter from all ",[22,310,311],{},"listen"," directives; in older versions, only the latter. Then reload and check that the old workers have exited. Check services that require HTTP\u002F2, such as gRPC, beforehand.",[223,314,315,318,319,322,323,326,327,330],{},[226,316,317],{},"Find where HTTP\u002F2 is active:"," ",[22,320,321],{},"nginx -T | grep -n http2"," shows the places in the configuration. From the outside, ",[22,324,325],{},"curl -sI --http2 https:\u002F\u002Fbeispiel-gmbh.at -o \u002Fdev\u002Fnull -w '%{http_version}\\n'"," prints ",[22,328,329],{},"2"," if the server negotiates HTTP\u002F2.",[223,332,333,336],{},[226,334,335],{},"Do not forget the rest of the release:"," disabling HTTP\u002F2 only protects against these two flaws. The other eight CVEs concern HTTP\u002F3, the resolver, the mail proxy and other modules; only the update helps there.",[223,338,339,342,343,346,347,350,351,83],{},[226,340,341],{},"Harden the kernel:"," where SCTP is not needed, block the module with ",[22,344,345],{},"install sctp \u002Fbin\u002Ffalse"," in a file under ",[22,348,349],{},"\u002Fetc\u002Fmodprobe.d\u002F",", as Xint recommends. This only prevents loading via ",[22,352,353],{},"modprobe",[223,355,356,359,360,363],{},[226,357,358],{},"Watch for signs:"," crashed workers in the error log (",[22,361,362],{},"exited on signal 11","), long-lived HTTP\u002F2 connections with very large data volumes, commands launched by an nginx worker. Wiz calls these general warning signs, not confirmed indicators.",[15,365,367],{"id":366},"what-helps-and-why-visibility-decides","What helps – and why visibility decides",[11,369,370,371,375,376,380,381,385,386,388,389,391],{},"On the day of an nginx update, the first question is not how to update but where nginx is running at all: as a web server, as a reverse proxy in front of applications, as ingress in a cluster, embedded in appliances. Through ",[35,372,374],{"href":373},"\u002Fen\u002Fplatform\u002Fattack-surface-management","Attack Surface Management",", blacklens.io continuously discovers from the outside which services, web applications and technologies are reachable; internal systems are covered by the ",[35,377,379],{"href":378},"\u002Fen\u002Fplatform\u002Fsentry","Sentry Agent",". The ",[35,382,384],{"href":383},"\u002Fen\u002Fplatform\u002Femerging-threats","Threat Center"," matches new CVEs such as ",[22,387,24],{}," against that inventory and shows for each hit whether it rests on the exact version or only on the product. For an nginx with ",[22,390,270],{},", it is the latter.",[11,393,394,395,397,398,401],{},"Two things the outside view does not show: whether a distribution package already contains the backport, and whether the conditions for ",[22,396,28],{}," are met. Whether HTTP\u002F2 is active, the ",[22,399,400],{},"curl"," command above shows in seconds. What can be narrowed down from the outside is where the check on the system is needed first.",{"title":403,"searchDepth":404,"depth":404,"links":405},"",3,[406,408,409,410,411,412,413],{"id":17,"depth":407,"text":18},2,{"id":86,"depth":407,"text":87},{"id":175,"depth":407,"text":176},{"id":196,"depth":407,"text":197},{"id":214,"depth":407,"text":215},{"id":274,"depth":407,"text":275},{"id":366,"depth":407,"text":367},"threat","2026-11-18","CVE-2026-123007 and CVE-2026-123633 in the nginx HTTP\u002F2 module allow unauthenticated code execution. Who is affected and what helps until you can patch.",false,"md",[420,422,425,428],{"q":18,"a":421},"CVE-2026-123007 and CVE-2026-123633 are two memory-safety flaws in the nginx HTTP\u002F2 module that let attackers execute code on the server without authentication. CVE-2026-123007 is a calculation error in HTTP\u002F2 flow control and has been in the code since nginx 1.9.5 in 2015. CVE-2026-123633 is a use-after-free that can occur since nginx 1.19.7. F5 rates both at CVSS 9.2 under version 4.0. Both were fixed on 18 November 2026.",{"q":423,"a":424},"Which nginx versions are affected by the HTTP\u002F2 flaws?","CVE-2026-123007 affects nginx 1.9.5 to 1.31.8, and CVE-2026-123633 affects nginx 1.19.7 to 1.31.8, in both cases only with HTTP\u002F2 enabled. Both are fixed in nginx 1.30.7 (stable) and 1.31.9 (mainline) and in NGINX Plus 37.0.8.1 and 37.3.0.1. Distributions such as Debian and Ubuntu usually ship fixes as backports under the old version number. There, the distribution's security notice is what counts, not the nginx version string.",{"q":426,"a":427},"How do I disable HTTP\u002F2 in nginx until the update is installed?","From nginx 1.25.1, HTTP\u002F2 is disabled with the directive http2 off; in every affected server block, and the http2 parameter must also be removed from all listen directives. In older versions, removing http2 from the listen lines is enough. Then reload nginx and check that the old worker processes have exited. This closes the attack path for both HTTP\u002F2 flaws, but not for the other eight bugs fixed in the same release.",{"q":429,"a":430},"How does blacklens.io help with the nginx HTTP\u002F2 flaws?","blacklens.io uses Attack Surface Management to continuously discover from the outside which services, web applications and technologies an organisation exposes, and the Threat Center matches new CVEs against that inventory, showing for each hit whether it rests on the exact version or only on the product. For the nginx flaws, this shows where nginx is reachable from the internet. Whether HTTP\u002F2 is active and a distribution package contains the backport is checked on the system.","\u002Fimages\u002Finsights\u002Fnginx-http2-lucken-codeausfuhrung-ohne-anmeldung.webp","Diagram: four HTTP\u002F2 streams run as frames towards a server, one shoots red past a dashed limit","en",null,{},true,"\u002Fen\u002Finsights\u002Fnginx-http2-lucken-codeausfuhrung-ohne-anmeldung",7,{"title":5,"description":416},{"loc":437},"en\u002Finsights\u002Fnginx-http2-lucken-codeausfuhrung-ohne-anmeldung",[443],"Threat landscape","nginx-http2-lucken-codeausfuhrung-ohne-anmeldung","mkudMubuFx80Q6A2Bw6vZsXyRAcvr8WEnLDF4fD-I-M",[447,882,1289],{"id":448,"title":449,"author":6,"body":450,"category":414,"date":415,"description":858,"draft":417,"extension":418,"faq":859,"image":871,"imageAlt":872,"lang":433,"legacyUrl":434,"meta":873,"navigation":436,"path":874,"readingTime":875,"seo":876,"sitemap":877,"stem":878,"tags":879,"translation":880,"updated":434,"__hash__":881},"insightsEn\u002Fen\u002Finsights\u002Fjava4shell-cpu-entscheidet-ob-java-verwundbar-ist.md","Java4Shell: the CPU decides whether Java is vulnerable",{"type":8,"value":451,"toc":850},[452,455,459,476,498,502,505,536,539,542,551,565,569,572,575,588,599,603,606,745,767,769,772,830,833,835,847],[11,453,454],{},"Since the evening of 17 November 2026 there have been updates for Java4Shell, a flaw that has been in OpenJDK since release 17.0.6. Even so, only some systems are vulnerable. The same application on the same JDK can be attacked on one server and not on the next, because the faulty code runs only on certain processors. Whether an affected system can be patched today depends in turn on who supplies its JDK.",[15,456,458],{"id":457},"what-is-java4shell","What is Java4Shell?",[11,460,461,462,465,466,469,470,475],{},"Java4Shell is the name under which the security company Calif.io published ",[22,463,464],{},"CVE-2026-114938"," on 17 November 2026: an out-of-bounds write in the Base64 decoder of OpenJDK's HotSpot JVM. For processors with AVX-512, HotSpot ships a hand-written assembly routine, and that is where the bug sits. If an input ends in an incomplete block with the padding character ",[22,467,468],{},"=",", the routine calculates a negative remaining length and writes a full block of 64 bytes, in ",[35,471,474],{"href":472,"rel":473},"https:\u002F\u002Fcalif.io\u002Fjava4shell",[39],"Calif's example"," 62 of them past the end of the buffer. Java then rejects the input as invalid. By that point neighbouring objects in memory have already been overwritten.",[11,477,478,479,482,483,485,486,488,489,494,495,497],{},"According to Calif, 64 times ",[22,480,481],{},"A"," followed by one ",[22,484,468],{}," is enough to trigger it; on OpenJDK 17 it takes 128 times ",[22,487,481],{},". Those involved do not agree on severity. Oracle rates the flaw in the ",[35,490,493],{"href":491,"rel":492},"https:\u002F\u002Fwww.cve.org\u002FCVERecord?id=CVE-2026-114938",[39],"CVE record"," at ",[35,496,45],{"href":44}," 8.1 under version 3.1 and calls it \"difficult to exploit\". Calif arrives at 9.2 under version 4.0, and Red Hat provisionally at 9.8.",[15,499,501],{"id":500},"three-conditions-version-processor-decoder","Three conditions: version, processor, decoder",[11,503,504],{},"A JVM is vulnerable only when three conditions hold at once:",[220,506,507,516,522],{},[223,508,509,512,513,83],{},[226,510,511],{},"The version:"," OpenJDK 17.0.6 and later in the 17, 21, 25 and 27 lines, whoever the vendor. The standard builds of Java 8 and 11 do not contain the routine. The one exception in the CVE record is Oracle's Java 8 Enterprise Performance Pack ",[22,514,515],{},"8u511b33-perf",[223,517,518,521],{},[226,519,520],{},"The processor:"," x86-64 with the AVX-512 VBMI instruction set extension, which mainly means Intel Xeon from the Ice Lake generation onwards and AMD EPYC and Ryzen from Zen 4 onwards. On ARM64 and on older x86 processors the JVM takes a different code path that does not contain the bug.",[223,523,524,527,528,531,532,535],{},[226,525,526],{},"The decoder:"," the application has to pass untrusted data to ",[22,529,530],{},"Base64.getDecoder()"," or ",[22,533,534],{},"Base64.getUrlDecoder()",". Before authentication this happens, according to Upwind, in HTTP Basic auth in Spring Security, Tomcat and Jetty 12, and in the java-jwt library.",[11,537,538],{},"The second condition changes the stocktake: a list of Java versions no longer answers the question of exposure on its own. In the cloud, Red Hat names the AWS families C6i, M6i and C7i, Google's C3 and N4 and Azure's D-series v5 to v7 among those most likely to be affected; ARM instances such as Graviton are not. When a workload moves to a different instance type, the answer changes. The routine also becomes active only once the JVM has compiled the decoder after frequent use, so a single test call does not trigger the bug.",[11,540,541],{},"Processor and JVM can both be checked on the system itself:",[543,544,549],"pre",{"className":545,"code":547,"language":548,"meta":403},[546],"language-text","grep -m1 '^flags' \u002Fproc\u002Fcpuinfo | tr ' ' '\\n' | grep -E '^(avx512f|avx512bw|avx512vbmi|bmi2)$'\njava -XX:+PrintFlagsFinal -version | grep -E 'UseAVX|UseBASE64Intrinsics'\n","text",[22,550,547],{"__ignoreMap":403},[11,552,553,554,557,558,561,562,564],{},"If the first command prints all four flags, the processor meets the condition. If ",[22,555,556],{},"UseAVX"," is also above 2 and ",[22,559,560],{},"UseBASE64Intrinsics"," is ",[22,563,252],{},", the faulty path is live in that JVM.",[15,566,568],{"id":567},"how-far-the-attack-goes","How far the attack goes",[11,570,571],{},"What has been shown publicly so far is a JVM crash; Calif and a few other researchers report code execution without publishing their exploits. Calif says it executed code without authentication in the default configurations of Keycloak, Jira, Confluence, Artifactory, Jenkins and PingFederate, and after authentication in Kafka, Solr, Elasticsearch, Gerrit and Spinnaker. By its account there is no universal exploit: every target needs its own preparation of the heap, and a failed attempt can crash the JVM.",[11,573,574],{},"Other labs confirm the bug and are more cautious about its consequences. VulnCheck reproduced it on Ice Lake hardware and calls the crash \"trivial\" once an input reaches the decoder; code execution, it says, requires non-trivial heap grooming and a target-specific memory leak. At the same time VulnCheck says it already offers its customers a full exploit.",[11,576,577,578,583,584,587],{},"No attacks in the wild are known as of 18 November. The Canadian Centre for Cyber Security says in its ",[35,579,582],{"href":580,"rel":581},"https:\u002F\u002Fwww.cyber.gc.ca\u002Fen\u002Falerts-advisories\u002Fal26-029-critical-vulnerability-impacting-oracle-java-cve-2026-114938",[39],"alert of 17 November"," that it is not aware of active exploitation, and the flaw is not in the ",[35,585,586],{"href":185},"CISA KEV catalogue",". CISA nevertheless urges immediate patching in an alert of its own.",[11,589,590,591,595,596,83],{},"Calif says it found the flaw with AI, as it did ",[35,592,594],{"href":593},"\u002Fen\u002Finsights\u002Fphp2shell-kritische-rce-lucken-in-php","PHP2Shell"," in October: one hour to the finding, two more to the first working exploit, at a cost of under 200 US dollars. The effort per target, on which the cautious assessments rest, is therefore smaller than it used to be. That trend ",[35,597,598],{"href":81},"has been apparent since April",[15,600,602],{"id":601},"who-already-has-a-fix-and-who-does-not","Who already has a fix – and who does not",[11,604,605],{},"As of 18 November, Oracle, Amazon and Azul ship a fix; Eclipse Temurin, Red Hat and Debian have not yet published a corrected build.",[92,607,608,621],{},[95,609,610],{},[98,611,612,615,618],{},[101,613,614],{},"JDK",[101,616,617],{},"Release with the fix",[101,619,620],{},"Status on 18 November",[108,622,623,648,669,690,710,723],{},[98,624,625,628,645],{},[113,626,627],{},"Oracle Java SE",[113,629,630,67,633,67,636,67,639,67,642],{},[22,631,632],{},"17.0.21.1",[22,634,635],{},"21.0.13.1",[22,637,638],{},"25.0.5.1",[22,640,641],{},"27.0.1.1",[22,643,644],{},"8u513-perf",[113,646,647],{},"since 17 November",[98,649,650,653,667],{},[113,651,652],{},"Amazon Corretto",[113,654,655,67,658,67,661,67,664],{},[22,656,657],{},"17.0.21.1.2",[22,659,660],{},"21.0.13.1.2",[22,662,663],{},"25.0.5.1.2",[22,665,666],{},"27.0.1.1.4",[113,668,647],{},[98,670,671,674,688],{},[113,672,673],{},"Azul Zulu",[113,675,676,67,679,67,682,67,685],{},[22,677,678],{},"17.70.201",[22,680,681],{},"21.54.201",[22,683,684],{},"25.38.201",[22,686,687],{},"27.30.201",[113,689,647],{},[98,691,692,695,698],{},[113,693,694],{},"Eclipse Temurin",[113,696,697],{},"none yet",[113,699,700,701,67,704,67,707],{},"latest releases ",[22,702,703],{},"17.0.21+9",[22,705,706],{},"21.0.13+9",[22,708,709],{},"25.0.5+8",[98,711,712,715,717],{},[113,713,714],{},"Red Hat (RHEL 8, 9, 10)",[113,716,697],{},[113,718,719,720],{},"errata announced, bulletin ",[22,721,722],{},"RHSB-2026-018",[98,724,725,728,730],{},[113,726,727],{},"Debian",[113,729,697],{},[113,731,732,67,735,67,738,25,741,744],{},[22,733,734],{},"openjdk-17",[22,736,737],{},"-21",[22,739,740],{},"-25",[22,742,743],{},"-27"," listed as \"vulnerable\"",[11,746,747,748,750,751,754,755,760,761,766],{},"Two things are easily missed during the check. The corrected OpenJDK releases differ only in the fourth position: ",[22,749,632],{}," contains the fix, ",[22,752,753],{},"17.0.21"," does not. And many Java applications bring their own runtime. According to ",[35,756,759],{"href":757,"rel":758},"https:\u002F\u002Fwww.cisa.gov\u002Fnews-events\u002Falerts\u002F2026\u002F11\u002F17\u002Fcritical-java-vulnerability-requires-immediate-patching",[39],"CISA",", JDKs inside third-party applications, container images and appliances often do not appear as separate entries in software inventories. ",[35,762,765],{"href":763,"rel":764},"https:\u002F\u002Faccess.redhat.com\u002Fsecurity\u002Fvulnerabilities\u002FRHSB-2026-018",[39],"Red Hat"," advises applying the start-up option or the update through the vendor there, rather than replacing the bundled JVM yourself.",[15,768,275],{"id":274},[11,770,771],{},"The order follows from the three conditions:",[220,773,774,780,789,803,812],{},[223,775,776,779],{},[226,777,778],{},"Inventory the runtimes",", with vendor and full build number, including those inside applications, container images and appliances. Internet-facing services come first, login services above all.",[223,781,782,318,785,788],{},[226,783,784],{},"Update where a fix exists, and restart the process.",[22,786,787],{},"jcmd \u003CPID> VM.version"," shows which release is actually running.",[223,790,791,794,795,798,799,802],{},[226,792,793],{},"Otherwise switch off the code path."," Red Hat recommends ",[22,796,797],{},"-XX:-UseBASE64Intrinsics","; VulnCheck, Datadog and Upwind have tested that the overflow no longer occurs with it. ",[22,800,801],{},"-XX:UseAVX=2"," turns off AVX-512 altogether and belongs on x86-64 only: a JVM on ARM will not start with it.",[223,804,805,318,808,811],{},[226,806,807],{},"Test start-up options before rolling them out.",[22,809,810],{},"-XX:DisableIntrinsic=_base64_decodeBlock",", which is also circulating, stops the JVM from starting when set on its own, according to Upwind.",[223,813,814,817,818,821,822,825,826,829],{},[226,815,816],{},"Watch for signals:"," bursts of ",[22,819,820],{},"IllegalArgumentException"," from ",[22,823,824],{},"java.util.Base64",", unexplained ",[22,827,828],{},"hs_err_pid*.log"," files and restarts. None of these proves an attack.",[11,831,832],{},"What does not help: size limits on the reverse proxy. Depending on the version, the triggering input is only 65 or 129 characters long.",[15,834,367],{"id":366},[11,836,837,838,375,840,380,842,385,844,846],{},"The question on the day of an update like this is not how to update Java, but where a JVM is running at all. Through ",[35,839,374],{"href":373},[35,841,379],{"href":378},[35,843,384],{"href":383},[22,845,464],{}," against that inventory in real time and shows for each hit whether it rests on the exact version or only on the product.",[11,848,849],{},"With Java4Shell the limit is clear: which processor sits beneath a JVM, and which JDK an application bundles, is not something any service reveals from the outside. That check stays on the system. What can be narrowed down from the outside is where it is needed first.",{"title":403,"searchDepth":404,"depth":404,"links":851},[852,853,854,855,856,857],{"id":457,"depth":407,"text":458},{"id":500,"depth":407,"text":501},{"id":567,"depth":407,"text":568},{"id":601,"depth":407,"text":602},{"id":274,"depth":407,"text":275},{"id":366,"depth":407,"text":367},"Java4Shell (CVE-2026-114938) hits OpenJDK 17.0.6 and later only on x86 servers with AVX-512 VBMI. Which JDKs have a fix, and what helps until then.",[860,862,865,868],{"q":458,"a":861},"Java4Shell is the name for CVE-2026-114938, an out-of-bounds write in the Base64 decoder of OpenJDK's HotSpot JVM. The security company Calif.io published the flaw on 17 November 2026, and Oracle fixed it the same day. A crafted Base64 value makes the decoder write past the end of its output buffer. The result can be a JVM crash and, according to Calif, remote code execution without authentication. Oracle rates the flaw CVSS 8.1, Calif 9.2 under version 4.0.",{"q":863,"a":864},"Which Java versions and processors are affected by Java4Shell?","Java4Shell affects OpenJDK 17.0.6 and later in the 17, 21, 25 and 27 lines, in the builds of every vendor, from Oracle and Amazon Corretto to Eclipse Temurin and Red Hat. The faulty code only runs on x86-64 processors with AVX-512 VBMI, though, which mainly means Intel Xeon from Ice Lake onwards and AMD from Zen 4 onwards. ARM64 systems are not affected, nor are the standard builds of Java 8 and 11. One exception is Oracle's Java 8 Enterprise Performance Pack 8u511b33-perf.",{"q":866,"a":867},"What can I do if there is no fix for my JDK yet?","Until the JDK vendor ships a corrected build, the faulty code path behind Java4Shell can be switched off when the JVM starts. Red Hat recommends the option -XX:-UseBASE64Intrinsics, which disables only the accelerated Base64 processing. The alternative, -XX:UseAVX=2, turns off AVX-512 altogether and must only be set on x86-64, because a JVM on ARM will not start with it. Both options take effect only after the process restarts, and neither replaces the update.",{"q":869,"a":870},"How does blacklens.io help with Java4Shell?","blacklens.io continuously discovers from the outside, through Attack Surface Management, which of an organisation's services, web applications and technologies are reachable, and the Threat Center matches new CVEs against that inventory in real time, stating for each hit whether it rests on the exact version or only on the product. For Java4Shell this shows where Java applications are reachable from the internet. The processor and a bundled JDK are not visible from the outside and are checked on the system.","\u002Fimages\u002Finsights\u002Fjava4shell-cpu-entscheidet-ob-java-verwundbar-ist.webp","Diagram: below a processor symbol, a write runs past the end of a green buffer into red neighbouring cells",{},"\u002Fen\u002Finsights\u002Fjava4shell-cpu-entscheidet-ob-java-verwundbar-ist",6,{"title":449,"description":858},{"loc":874},"en\u002Finsights\u002Fjava4shell-cpu-entscheidet-ob-java-verwundbar-ist",[443],"java4shell-cpu-entscheidet-ob-java-verwundbar-ist","A_CKiM9Eiujhm6ctqpce6FXfliwi3r4ON03827NtIrw",{"id":883,"title":884,"author":6,"body":885,"category":1261,"date":1262,"description":1263,"draft":417,"extension":418,"faq":1264,"image":1274,"imageAlt":1275,"lang":433,"legacyUrl":434,"meta":1276,"navigation":436,"path":1277,"readingTime":875,"seo":1278,"sitemap":1279,"stem":1284,"tags":1285,"translation":1287,"updated":434,"__hash__":1288},"insightsEn\u002Fen\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen.md","NIS2 supply chain: what happens between two questionnaires",{"type":8,"value":886,"toc":1248},[887,890,894,902,944,947,951,959,989,998,1002,1010,1072,1075,1079,1082,1121,1125,1128,1148,1151,1155,1163,1168,1175,1182,1186,1189,1196,1202,1206,1213,1219,1230,1234,1240],[11,888,889],{},"A supplier questionnaire records how secure a supplier was on the day it was filled in. Your supply chain's security is decided on the other 364 days: by the IT provider that leaves its VPN gateway unpatched, the tax adviser whose domain can be spoofed, the logistics partner that turns up on a ransomware leak site. NIS2 requires you to account for exactly these weaknesses in every direct supplier. That means knowing them before the next questionnaire is due.",[15,891,893],{"id":892},"what-nis2-requires-for-the-supply-chain","What NIS2 requires for the supply chain",[11,895,896,897,901],{},"The ",[35,898,900],{"href":899},"\u002Fen\u002Fwissen\u002Fnis2","NIS2 Directive"," makes supply chain security a mandatory risk management measure. Article 21(2)(d) names it; Article 21(3) requires organisations to consider the vulnerabilities specific to each direct supplier and the quality of its cybersecurity practices. Nationally and by sector:",[220,903,904,915,926,938],{},[223,905,906,318,909,914],{},[226,907,908],{},"Austria:",[35,910,913],{"href":911,"rel":912},"https:\u002F\u002Fwww.ris.bka.gv.at\u002FDokumente\u002FBundesnormen\u002FNOR40273893\u002FNOR40273893.html",[39],"Section 32(4)(d) NISG 2026",", in force since 1 October 2026, adopts this wording, including the vulnerabilities of each supplier.",[223,916,917,318,920,925],{},[226,918,919],{},"Germany:",[35,921,924],{"href":922,"rel":923},"https:\u002F\u002Fwww.gesetze-im-internet.de\u002Fbsig_2025\u002F__30.html",[39],"Section 30(2) no. 4 of the BSI Act"," names supply chain security, in force since 6 December 2025.",[223,927,928,931,932,937],{},[226,929,930],{},"Digital providers"," such as cloud, data centre and managed service providers: under point 5.1.6 of the annex to ",[35,933,936],{"href":934,"rel":935},"https:\u002F\u002Feur-lex.europa.eu\u002Feli\u002Freg_impl\u002F2024\u002F2690\u002Foj\u002Feng",[39],"Implementing Regulation (EU) 2024\u002F2690",", they monitor and evaluate changes in suppliers' cybersecurity practices, for example after significant incidents, and act where necessary.",[223,939,940,943],{},[226,941,942],{},"Financial sector:"," DORA covers ICT third-party risk in Articles 28 to 30.",[11,945,946],{},"ISO 27001 control A.5.22 is more specific: supplier security practices must be monitored, reviewed and evaluated regularly. None of these rules prescribes a tool or an interval. All assume you notice changes at a supplier when they happen.",[15,948,950],{"id":949},"why-the-questionnaire-alone-falls-short","Why the questionnaire alone falls short",[11,952,953,954,958],{},"A questionnaire is a dated self-declaration: it records what a supplier says about itself, once. It keeps its place in ",[35,955,957],{"href":956},"\u002Fen\u002Fwissen\u002Fthird-party-risk-management","third-party risk management",", because nobody sees processes, backups or training from outside. For the systems a supplier exposes to the internet, it has three gaps:",[220,960,961,977,983],{},[223,962,963,966,967,970,971,976],{},[226,964,965],{},"It goes stale."," In 2026, the US agency CISA added 283 vulnerabilities to its ",[35,968,969],{"href":185},"catalogue of known exploited vulnerabilities"," by early November, more than six a week (",[35,972,975],{"href":973,"rel":974},"https:\u002F\u002Fwww.cisa.gov\u002Fknown-exploited-vulnerabilities-catalog",[39],"as of 3 November 2026","). More than two dozen hit firewalls, VPN and remote access gateways, the systems service providers use to reach customer networks.",[223,978,979,982],{},[226,980,981],{},"It doesn't measure."," \"We patch promptly\" is an answer, not a finding. No questionnaire tells you whether the provider's VPN gateway reports a vulnerable version.",[223,984,985,988],{},[226,986,987],{},"It doesn't scale."," With a few hundred suppliers, one round a year is already a project, for you and for suppliers asked the same questions by many customers.",[11,990,991,992,997],{},"Verizon's ",[35,993,996],{"href":994,"rel":995},"https:\u002F\u002Fwww.verizon.com\u002Fabout\u002Fnews\u002Fbreach-industry-wide-dbir-finds",[39],"2026 Data Breach Investigations Report"," puts the risk in numbers: a third party was involved in 48 per cent of confirmed breaches, up from 30 per cent in the previous report.",[15,999,1001],{"id":1000},"what-an-outside-in-rating-shows-and-what-it-doesnt","What an outside-in rating shows, and what it doesn't",[11,1003,1004,1005,1009],{},"An outside-in rating, also called a ",[35,1006,1008],{"href":1007},"\u002Fen\u002Fwissen\u002Fsecurity-rating","security rating",", measures what a supplier's internet-facing infrastructure reveals, without access to its systems or its involvement. It answers part of the questionnaire with a measurement, not a statement:",[92,1011,1012,1022],{},[95,1013,1014],{},[98,1015,1016,1019],{},[101,1017,1018],{},"Questionnaire question",[101,1020,1021],{},"Measurable from outside",[108,1023,1024,1032,1040,1048,1056,1064],{},[98,1025,1026,1029],{},[113,1027,1028],{},"Do you apply security updates promptly?",[113,1030,1031],{},"Outdated software and known vulnerabilities on reachable systems",[98,1033,1034,1037],{},[113,1035,1036],{},"Is remote access secured?",[113,1038,1039],{},"Exposed remote maintenance, VPN and admin access",[98,1041,1042,1045],{},[113,1043,1044],{},"Do you encrypt data in transit?",[113,1046,1047],{},"Certificates, TLS versions and cipher suites",[98,1049,1050,1053],{},[113,1051,1052],{},"Is your e-mail domain protected against spoofing?",[113,1054,1055],{},"SPF, DKIM and DMARC records",[98,1057,1058,1061],{},[113,1059,1060],{},"Have you had security incidents?",[113,1062,1063],{},"Leaked credentials, listings on ransomware leak sites",[98,1065,1066,1069],{},[113,1067,1068],{},"Do you have backups, incident plans and training?",[113,1070,1071],{},"Not measurable; stays with questionnaire and audit",[11,1073,1074],{},"The last row is the key limit. A good grade means no obvious weaknesses from outside, not that the supplier is secure, and only what can be attributed to its domain is rated. The rating does not replace the questionnaire. It shows which supplier to ask, and when.",[15,1076,1078],{"id":1077},"how-to-set-up-continuous-supplier-monitoring","How to set up continuous supplier monitoring",[11,1080,1081],{},"Continuous supplier monitoring needs no big project, just six decisions you make once:",[1083,1084,1085,1091,1097,1103,1109,1115],"ol",{},[223,1086,1087,1090],{},[226,1088,1089],{},"Start from procurement's list."," The vendor list in your ERP beats any list from memory; what counts is each supplier's domain.",[223,1092,1093,1096],{},[226,1094,1095],{},"Rank by criticality."," Does the supplier access your systems? Does it process confidential data? Would your operation stop without it? Two yeses make it critical.",[223,1098,1099,1102],{},[226,1100,1101],{},"Record the baseline."," Change matters more than the absolute value: a supplier falling from B to D deserves more attention than one steady at C for a year.",[223,1104,1105,1108],{},[226,1106,1107],{},"Define triggers and owners."," Triggers might be a new known exploited vulnerability, a leak-site listing or a D or F grade for a critical supplier; owners can be security, procurement or the business unit.",[223,1110,1111,1114],{},[226,1112,1113],{},"Review weekly."," A fixed weekly slot is enough when alerts cover the urgent cases.",[223,1116,1117,1120],{},[226,1118,1119],{},"File the evidence."," A monthly report with date, grade distribution and your responses to declines belongs in the ISMS.",[15,1122,1124],{"id":1123},"what-to-do-when-a-supplier-gets-worse","What to do when a supplier gets worse",[11,1126,1127],{},"A worse rating is a reason to ask, not a verdict. How urgently you respond depends on the cause:",[220,1129,1130,1136,1142],{},[223,1131,1132,1135],{},[226,1133,1134],{},"Known exploited vulnerability:"," Send the supplier's security contact the finding with system, CVE and date, and agree a fix date. Until then, restrict its VPN accounts or API keys on your side.",[223,1137,1138,1141],{},[226,1139,1140],{},"Ransomware leak-site listing:"," Treat it as a possible incident of your own. Establish which of your data the supplier holds, rotate shared credentials and check whether your own services are significantly disrupted. If they are, your reporting duty under NIS2 Article 23 may apply.",[223,1143,1144,1147],{},[226,1145,1146],{},"Unprotected e-mail domain:"," Without an enforced DMARC policy, e-mails in the supplier's name are easier to forge, invoices with changed bank details included. Until the next review, have accounts confirm bank detail changes via a known phone number.",[11,1149,1150],{},"Record every response: who contacted whom and when, what the supplier answered and what you decided. This chain of finding, contact and decision shows you actually take your suppliers' vulnerabilities into account.",[15,1152,1154],{"id":1153},"how-blacklensio-takes-over-continuous-monitoring","How blacklens.io takes over continuous monitoring",[11,1156,1157,1158,1162],{},"In blacklens.io, the ",[35,1159,1161],{"href":1160},"\u002Fen\u002Fsolutions\u002Fsupply-chain-monitoring","Supply Chain Monitoring"," module handles the steps that take time: measuring, repeating, comparing. Your supplier has nothing to install or approve. The images show the demo workspace with fictional suppliers.",[1164,1165,1167],"h3",{"id":1166},"import-and-rank-suppliers","Import and rank suppliers",[11,1169,1170,1171,1174],{},"Under ",[226,1172,1173],{},"Supply Chain → Suppliers"," you add suppliers one by one, as a list or as a CSV file from procurement. URLs and e-mail addresses are reduced to the registrable domain, and a preview shows every entry before anything is added. Criticality (Low to Critical) and tags are set during import.",[11,1176,1177],{},[1178,1179],"img",{"alt":1180,"src":1181},"The Add suppliers drawer in blacklens.io: a URL, an e-mail address and a subdomain become domains, a duplicate and an IP address are rejected","\u002Fimages\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen-2.webp",[1164,1183,1185],{"id":1184},"rating-and-baseline","Rating and baseline",[11,1187,1188],{},"Each supplier gets a grade from A to F and a score from 0 to 100 across nine rating areas, from software patching to e-mail and DNS security. The first rating starts automatically and is the baseline; a new one follows every 7 days. Areas that cannot be measured do not count as 0. Every finding states what was found and how to fix it; pass it on as a CSV export or Supplier Report (PDF).",[11,1190,1191,1192,1195],{},"In the demo workspace, a managed service provider rated Critical, which runs the Microsoft 365 tenant, operates a VPN gateway with ",[22,1193,1194],{},"CVE-2024-3400",", in the CISA KEV catalogue since April 2024. While the finding stands, the grade is capped at D. Without the cap, it would be a C.",[11,1197,1198],{},[1178,1199],{"alt":1200,"src":1201},"Demo supplier in blacklens.io: grade capped at D, below it the finding CVE-2024-3400 with what was found and how to fix it","\u002Fimages\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen-3.webp",[1164,1203,1205],{"id":1204},"alerts-and-the-weekly-review","Alerts and the weekly review",[11,1207,1208,1209,1212],{},"When a rating is worse than the last, the alert ",[226,1210,1211],{},"Supplier risk increased"," reports it by e-mail, push or to Microsoft Teams, Slack, Jira or ServiceNow. Triggers are a lower grade, a new known exploited vulnerability, a new critical finding or a ransomware leak-site listing. For Critical suppliers, severity rises to High. A falling score without a grade change raises no alert.",[11,1214,1215],{},[1178,1216],{"alt":1217,"src":1218},"Supplier risk increased alert with severity High: demo supplier dropped from B to D with a new known exploited vulnerability","\u002Fimages\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen-4.webp",[11,1220,1221,1222,1225,1226,1229],{},"For the weekly review, the supplier list shows the grade distribution, the last seven days' changes and tiles such as ",[226,1223,1224],{},"At risk"," (grade D or F). BQL filters such as ",[22,1227,1228],{},"criticality = critical and kev_findings > 0"," find critical suppliers with known exploited vulnerabilities. The ransomware watchlist also checks leak sites, about every 30 minutes.",[1164,1231,1233],{"id":1232},"evidence","Evidence",[11,1235,896,1236,1239],{},[226,1237,1238],{},"Supply Chain Report"," summarises the last 30 days of the portfolio as a PDF, with changes, risk concentrations and required action, one-off or scheduled monthly to fixed recipients. With the rating and alert history, it provides evidence for NIS2 and DORA.",[11,1241,1242,1243,1247],{},"blacklens.io does not cover questionnaires, self-assessments or a supplier portal. Each workspace licence includes five suppliers, and the 14-day trial includes ",[35,1244,1246],{"href":1245},"\u002Fen\u002Fplatform\u002Fsupplier-risk-rating","supplier risk rating",". The outside view makes sure the next questionnaire asks the right questions.",{"title":403,"searchDepth":404,"depth":404,"links":1249},[1250,1251,1252,1253,1254,1255],{"id":892,"depth":407,"text":893},{"id":949,"depth":407,"text":950},{"id":1000,"depth":407,"text":1001},{"id":1077,"depth":407,"text":1078},{"id":1123,"depth":407,"text":1124},{"id":1153,"depth":407,"text":1154,"children":1256},[1257,1258,1259,1260],{"id":1166,"depth":404,"text":1167},{"id":1184,"depth":404,"text":1185},{"id":1204,"depth":404,"text":1205},{"id":1232,"depth":404,"text":1233},"guide","2026-11-04","Supply chain security under NIS2: what Austria's NISG 2026 and Germany's BSIG require, where questionnaires end and how to monitor suppliers continuously.",[1265,1268,1271],{"q":1266,"a":1267},"How often do suppliers have to be assessed under NIS2?","NIS2 sets no fixed interval for assessing suppliers. Article 21 does require organisations to take into account the vulnerabilities specific to each direct supplier, which presupposes knowing their current state. For digital providers such as cloud and managed service providers, Implementing Regulation (EU) 2024\u002F2690 explicitly requires monitoring and evaluating changes in suppliers' cybersecurity practices. A workable combination is a questionnaire or audit for critical suppliers once a year, plus an outside-in rating that measures again every week.",{"q":1269,"a":1270},"What should you do when a supplier's security rating drops?","When a supplier's security rating drops, the reason sets the urgency. A known exploited vulnerability or a listing on a ransomware leak site calls for a response within days, while a missing DMARC policy belongs in the next supplier review. Send the supplier's security contact the specific finding with system, date and remediation advice, check in parallel what access the supplier has to your systems, and record contact, answer and decision as evidence.",{"q":1272,"a":1273},"How does blacklens.io monitor supplier security?","The Supply Chain Monitoring module in blacklens.io rates every supplier from the outside by its domain, with nothing for the supplier to install or approve. Each supplier receives a grade from A to F and a score from 0 to 100 across nine rating areas and is re-rated every 7 days. When a rating gets worse, the alert \"Supplier risk increased\" reports it by e-mail, push or integration. blacklens.io does not cover questionnaires or self-assessments.","\u002Fimages\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen.webp","Supplier list in blacklens.io with the A to F grade distribution, risk tiles and fictional demo suppliers",{},"\u002Fen\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen",{"title":884,"description":1263},{"loc":1277,"images":1280},[1281,1282,1283],{"loc":1181},{"loc":1201},{"loc":1218},"en\u002Finsights\u002Fnis2-lieferkette-lieferanten-laufend-uberwachen",[1286],"Guide","nis2-lieferkette-lieferanten-laufend-uberwachen","TlbMtKdts05TT42a1sUEUi4OxMGRzs_ppMPZypu3wng",{"id":1290,"title":1291,"author":6,"body":1292,"category":414,"date":1669,"description":1670,"draft":417,"extension":418,"faq":1671,"image":1680,"imageAlt":1681,"lang":433,"legacyUrl":434,"meta":1682,"navigation":436,"path":1683,"readingTime":1684,"seo":1685,"sitemap":1686,"stem":1687,"tags":1688,"translation":1689,"updated":434,"__hash__":1690},"insightsEn\u002Fen\u002Finsights\u002Fhttp2shell-brotli-lucke-jenseits-von-node-js.md","HTTP2Shell: the Brotli flaw reaches far beyond Node.js",{"type":8,"value":1293,"toc":1660},[1294,1306,1310,1326,1330,1333,1448,1463,1467,1477,1492,1499,1503,1544,1556,1560,1570,1576,1578,1581,1646,1648,1657],[11,1295,1296,1297,1300,1301,1305],{},"On 23 October, Node2Shell became HTTP2Shell – a new name, not a new flaw. It still means ",[22,1298,1299],{},"CVE-2026-111497"," in the Brotli decoder, whose consequences for Node.js are covered in ",[35,1302,1304],{"href":1303},"\u002Fen\u002Finsights\u002Fnode2shell-warum-node-patchen-nicht-reicht","yesterday's post",". What is new is how far the same library reaches: into Python packages, Bun, Envoy, curl and Git for Windows. There it becomes dangerous under one condition that many warnings leave out. The software has to decompress Brotli data from an untrusted source.",[15,1307,1309],{"id":1308},"what-is-http2shell","What is HTTP2Shell?",[11,1311,1312,1313,1315,1316,67,1319,25,1322,1325],{},"HTTP2Shell is the name the security firm Aikido gave, on 23 October 2026, to the reach of ",[22,1314,1299],{}," beyond Node.js: an out-of-bounds write in Google's Brotli decoder, affecting releases 1.0.3 to 1.2.0. The name shifts the focus from the runtime to the protocol. Any software that decompresses Brotli-compressed HTTP data can be affected. The bug, the fix and the corrected releases ",[22,1317,1318],{},"1.0.10",[22,1320,1321],{},"1.1.1",[22,1323,1324],{},"1.2.1"," are the same as on 21 October. Google itself issued the CVE record.",[15,1327,1329],{"id":1328},"who-is-affected-and-under-which-condition","Who is affected – and under which condition",[11,1331,1332],{},"Software is affected only if it contains a vulnerable Brotli release and uses it to decompress data an attacker can supply. For most of the projects now being named, exactly that is optional:",[92,1334,1335,1348],{},[95,1336,1337],{},[98,1338,1339,1342,1345],{},[101,1340,1341],{},"Component",[101,1343,1344],{},"Affected if",[101,1346,1347],{},"Fix",[108,1349,1350,1371,1390,1412,1434],{},[98,1351,1352,1361,1364],{},[113,1353,1354,1355,67,1358],{},"Python ",[22,1356,1357],{},"brotli",[22,1359,1360],{},"brotlicffi",[113,1362,1363],{},"requests, httpx or aiohttp find them installed",[113,1365,1366,531,1368],{},[22,1367,1324],{},[22,1369,1370],{},"1.2.1.0",[98,1372,1373,1376,1385],{},[113,1374,1375],{},"Bun",[113,1377,1378,531,1381,1384],{},[22,1379,1380],{},"fetch",[22,1382,1383],{},"node:zlib"," decodes Brotli",[113,1386,1387],{},[22,1388,1389],{},"1.4.4",[98,1391,1392,1395,1398],{},[113,1393,1394],{},"Envoy",[113,1396,1397],{},"the Brotli decompressor is configured",[113,1399,1400,67,1403,67,1406,67,1409],{},[22,1401,1402],{},"1.37.8",[22,1404,1405],{},"1.38.6",[22,1407,1408],{},"1.39.3",[22,1410,1411],{},"1.40.0",[98,1413,1414,1417,1423],{},[113,1415,1416],{},"Istio",[113,1418,1419,1420],{},"Brotli decompression is enabled, e.g. via ",[22,1421,1422],{},"EnvoyFilter",[113,1424,1425,67,1428,67,1431],{},[22,1426,1427],{},"1.29.9",[22,1429,1430],{},"1.30.6",[22,1432,1433],{},"1.31.2",[98,1435,1436,1439,1445],{},[113,1437,1438],{},"curl, libcurl",[113,1440,1441,1442],{},"built with Brotli and run with ",[22,1443,1444],{},"--compressed",[113,1446,1447],{},"update the Brotli library or the build",[11,1449,1450,1451,1454,1455,1458,1459,1462],{},"For Python, GitHub published a separate advisory on 22 October, ",[22,1452,1453],{},"GHSA-9v8h-qqgm-4m35",". The packages often enter an environment as an indirect dependency. Istio shipped the fix on 15 October, before disclosure. Copies built into a program need a new build: Git for Windows ",[22,1456,1457],{},"2.56.0.windows.3",", released on 22 October, still lists ",[22,1460,1461],{},"brotli 1.2.0-1"," in its package list.",[15,1464,1466],{"id":1465},"server-and-client-direction-decides","Server and client: direction decides",[11,1468,1469,1470,1473,1474,83],{},"The flaw works in both directions, and the second is easy to miss. On the server side, an application decompresses Brotli-compressed requests – in Node.js, for example, through the Express 5 parsers. On the client side, it decompresses the response of a server it calls itself. Bun and Node's ",[22,1471,1472],{},"fetch()"," do this automatically; urllib3, and with it requests, does so based on the response's ",[22,1475,1476],{},"Content-Encoding",[11,1478,1479,1480,1483,1484,1487,1488,1491],{},"On the client side, an attacker does not need to attack a server. They need to run one. Every feature that fetches an external address is such a route: webhooks, link previews, avatar imports, a ",[22,1481,1482],{},"git clone"," from an unknown server. A test published by the blog lilting.ch on 24 October shows urllib3 decoding a Brotli response even when the client asked for no compression with ",[22,1485,1486],{},"Accept-Encoding: identity",". A reverse proxy that rejects requests carrying ",[22,1489,1490],{},"Content-Encoding: br"," does not protect this direction.",[11,1493,1494,1495,1498],{},"Bun's advisory states explicitly that there is no process-wide workaround; individual calls can be protected with ",[22,1496,1497],{},"decompress: false",". The common web servers, on the other hand, are rarely the route. Apache and nginx compress with Brotli but, according to Aikido, do not decompress by default.",[15,1500,1502],{"id":1501},"version-numbers-do-not-show-the-fix","Version numbers do not show the fix",[11,1504,1505,1506,25,1509,1512,1513,1516,1517,1520,1521,55,1524,1527,1528,1531,1532,1535,1536,1539,1540,1543],{},"Whether a component contains the fix cannot be read reliably from its Brotli version string. In ",[22,1507,1508],{},"24.22.1",[22,1510,1511],{},"26.12.1",", Node.js took over only the fix commit. The version file in its source tree still says ",[22,1514,1515],{},"1.2.0",", in ",[22,1518,1519],{},"22.23.4"," it says ",[22,1522,1523],{},"1.1.0",[22,1525,1526],{},"process.versions.brotli"," reports those values. Debian backported the fix: ",[22,1529,1530],{},"1.0.9-2+deb12u1"," for Bookworm (",[22,1533,1534],{},"DLA-4855-1",") and ",[22,1537,1538],{},"1.1.0-2+deb13u1"," for Trixie (",[22,1541,1542],{},"DSA-6582-1","), both dated 23 October. Anyone comparing only the upstream version will report patched systems as vulnerable.",[11,1545,1546,1547,1550,1551,1555],{},"Then there is the timeline. The fix commit ",[22,1548,1549],{},"0ed4268"," has been public in the Brotli repository since 27 February 2026, described as \"Detect and report invalid stream earlier.\" A release followed only on 21 October. For almost eight months the correction sat in the source code, but in no release that distributions and package managers ship. It was a silent fix, like Fortinet's recent ",[35,1552,1554],{"href":1553},"\u002Fen\u002Finsights\u002Ffortinet-hardening-release-patchen-ohne-advisory","hardening release",", only longer.",[15,1557,1559],{"id":1558},"how-critical-the-flaw-really-is","How critical the flaw really is",[11,1561,1562,1563,1565,1566,1569],{},"The situation has not escalated since 21 October; it has become clearer. It is now known where the decoder sits, and there are still no known attacks. Google rates the flaw ",[35,1564,45],{"href":44}," 9.2 under version 4.0, but the vector contains ",[22,1567,1568],{},"AT:P",": a successful attack depends on specific deployment conditions of the system. Others rate it lower. Node.js and Bun call it \"high\", Amazon Linux scores it 8.1 under CVSS 3.1, and Ubuntu gives it priority \"medium\".",[11,1571,1572,1573,1575],{},"CISA's assessment in the CVE record reads \"none\" for exploitation and \"no\" for automatable. As of 24 October, the flaw is not in the ",[35,1574,186],{"href":185},". The only documented code execution remains Imperva's exploit against Node.js, which did not succeed on every attempt. Since 21 October, more than 30 repositories with proofs of concept, test labs and check scripts for the CVE have appeared on GitHub. Whether any of them is a reliable exploit is unknown.",[15,1577,275],{"id":274},[11,1579,1580],{},"The work shifts from asking about the version to asking who decompresses untrusted data:",[220,1582,1583,1599,1612,1618,1624,1630],{},[223,1584,1585,1588,1589,25,1591,1593,1594,25,1596,1598],{},[226,1586,1587],{},"Check Python environments",", not just the project files. Bring ",[22,1590,1357],{},[22,1592,1360],{}," to ",[22,1595,1324],{},[22,1597,1370],{},", in container images too.",[223,1600,1601,1604,1605,1608,1609,1611],{},[226,1602,1603],{},"Rebuild embedded copies."," According to Bun, programs built with ",[22,1606,1607],{},"bun build --compile"," stay vulnerable until rebuilt with ",[22,1610,1389],{},". The same applies to statically linked curl.",[223,1613,1614,1617],{},[226,1615,1616],{},"Search proxy configurations."," Envoy and Istio reach the decoder only with an active Brotli decompressor; where one is configured, the update comes first.",[223,1619,1620,1623],{},[226,1621,1622],{},"Include outbound requests."," Services that fetch user-supplied addresses decompress responses from servers they do not control.",[223,1625,1626,1629],{},[226,1627,1628],{},"Update distribution packages"," and restart processes. As of 24 October, Ubuntu lists the flaw as \"needs evaluation\" and Amazon Linux 2023 its Brotli package as \"pending fix\". Dynamically linked programs such as curl benefit from the library update without a release of their own.",[223,1631,1632,1635,1636,1638,1639,1641,1642,1645],{},[226,1633,1634],{},"Check version findings against the fix level."," Brotli ",[22,1637,1515],{}," in Node ",[22,1640,1508],{},", or ",[22,1643,1644],{},"1.0.9"," in Debian Bookworm, is not a finding.",[15,1647,367],{"id":366},[11,1649,1650,1651,1653,1654,1656],{},"With HTTP2Shell, what matters is less which Brotli version is installed than which systems decompress untrusted data: public APIs, proxies, services that fetch user-supplied addresses. Through ",[35,1652,374],{"href":373},", blacklens.io continuously discovers from the outside which services and web applications are reachable and which technologies, in which versions, run on them. The ",[35,1655,384],{"href":383}," matches new CVEs against that inventory in real time and shows for each hit whether it rests on the exact version or only on the product.",[11,1658,1659],{},"The limit is narrower here than with Node2Shell. The CVE record names only Brotli as the affected product, a library that no service displays to the outside. What can be recognised are its carriers, such as Node.js applications and proxies. A Brotli package in a Python environment or a compiled program is found only by a check on the system. From the outside, you can narrow down where that check is needed first.",{"title":403,"searchDepth":404,"depth":404,"links":1661},[1662,1663,1664,1665,1666,1667,1668],{"id":1308,"depth":407,"text":1309},{"id":1328,"depth":407,"text":1329},{"id":1465,"depth":407,"text":1466},{"id":1501,"depth":407,"text":1502},{"id":1558,"depth":407,"text":1559},{"id":274,"depth":407,"text":275},{"id":366,"depth":407,"text":367},"2026-10-24","HTTP2Shell is not a new flaw but CVE-2026-111497 in any software with a Brotli decoder. Who is affected, and why the version number misleads.",[1672,1674,1677],{"q":1309,"a":1673},"HTTP2Shell is a name for CVE-2026-111497, an out-of-bounds write in Google's Brotli decoder in releases 1.0.3 to 1.2.0. The security firm Aikido introduced it on 23 October 2026 because the flaw affects not only Node.js, where it became known as Node2Shell, but also Python packages, Bun, Envoy and curl. It is the same vulnerability with the same fixes: Brotli 1.0.10, 1.1.1 and 1.2.1.",{"q":1675,"a":1676},"Are Python requests and httpx affected by HTTP2Shell?","Python requests and httpx are affected only if the same environment has the brotli package before 1.2.1 or brotlicffi before 1.2.1.0 installed. Neither ships its own Brotli decoder; both use these packages as soon as they are present, in httpx's case for example through the httpx[brotli] extra. They then decode Brotli responses from the servers they call automatically. Whether the packages are installed is shown by the environment itself, not by the project's dependency list.",{"q":1678,"a":1679},"How does blacklens.io help with HTTP2Shell?","blacklens.io continuously discovers from the outside, through Attack Surface Management, which services, web applications and technologies are reachable, and the Threat Center matches new CVEs against that inventory in real time, stating for each hit whether it rests on the exact version or only on the product. For HTTP2Shell this shows where carriers such as Node.js applications and proxies are reachable. The Brotli library itself is not visible from the outside and is checked on the system.","\u002Fimages\u002Finsights\u002Fhttp2shell-brotli-lucke-jenseits-von-node-js.webp","A person at a laptop with their head in their hands, behind a world map of red dots covered in warning symbols",{},"\u002Fen\u002Finsights\u002Fhttp2shell-brotli-lucke-jenseits-von-node-js",5,{"title":1291,"description":1670},{"loc":1683},"en\u002Finsights\u002Fhttp2shell-brotli-lucke-jenseits-von-node-js",[443],"http2shell-brotli-lucke-jenseits-von-node-js","QM7BlnvG1GTFBh9srilBTou1foA7VuZNEjggsveJJ0w",1795019614419]