Overview
Description
Statistics
- 27 Posts
- 42 Interactions
Fediverse
Broadcom announced a critical auth bypass in multiple VMWare products today, and there are reports it has been exploited for some time.
https://ifin.network/t/cve-2026-123890-critical-auth-bypass-in-broadcom-vmware-vcenter/1010
ARMORY CASTLE nutzt vCenter-Zero-Day CVE-2026-123890 aus
Mandiant und die Google Threat Intelligence Group haben weitere Details zu Aktivitäten der mutmaßlich chinanahen Gruppe ARMORY CASTLE veröffentlicht. Der Angreifer drang über eine Remote-Support-Appliance in ein Netzwerk ein, nutzte eine Zero-Day-Lücke in VMware vCenter aus und griff ESXi-Hosts ab.
https://www.all-about-security.de/armory-castle-nutzt-vcenter-zero-day-cve-2026-123890-aus/
Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT
A China-linked espionage group (Armory Castle, formerly UNC5221 and Warp Panda) exploited CVE-2026-123890 — a CVSS 9.8 authentication bypass in VMware vCenter’s Directory Service — as a zero-day for over two months, according to Mandiant and Google: after entering through a BeyondTrust zero-day, the group used a custom tool called Bonesaw to steal SAML signing material, forge tokens and create an SSO administrator account. Broadcom patched the flaw in vCenter 9.1.1.0200, 9.0.2.0200 and 8.0 U3m, but vCenter 7.0 is end-of-support with no patch; Mandiant urges organisations to patch and hunt for evidence of compromise. https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/
Newly Patched VMware vCenter Flaw Exploited as Zero-Day by Chinese APT
Tracked as CVE-2026-123890 (CVSS score of 9.8), the bug resides in the VMware Directory Service and could let remote, unauthenticated attackers obtain an authenticated session with administrator privileges.
They used a custom tool to exploit CVE-2026-123890, steal the Lightning Memory-Mapped Database (#LMDB ), extract SAML signing material, and create a single sign-on (SSO) administrator account. https://www.securityweek.com/newly-patched-vmware-vcenter-flaw-exploited-as-zero-day-by-chinese-apt/
VMware vCenter, CVE-2026-123890 (CVSS 9.8): bypass di autenticazione nel Directory Service, sessione da amministratore senza credenziali. Secondo Google (GTIG/Mandiant) sfruttata come zero-day da inizio settembre in una rete già compromessa. Patch Broadcom del 19/11, nessun workaround: 8.0 U3m, 9.0.2.0200, 9.1.1.0200 (7.0 solo con supporto esteso). Limita l'accesso di rete a vCenter.
https://cloud.google.com/blog/topics/threat-intelligence/armory-castle-exploits-vsphere
VMware vCenter : une faille critique exploitée comme zero-day depuis septembre 2026 https://www.it-connect.fr/vmware-vcenter-cve-2026-123890-zero-day/ #ActuCybersécurité #Vulnérabilités #Cybersécurité #VMware
CVE-2026-123890: How ARMORY CASTLE Used a vCenter Zero-Day to Reach ESXi
ARMORY CASTLE exploited vCenter zero-day CVE-2026-123890 since September 2026. See the BONESAW attack chain, patched builds, and a hunting checklisthttps://thecybersecguru.com/exploits/cve-2026-123890-armory-castle-vcenter-zero-day/
#Schwachstellen in #vCenter. Die Authenification Bypass-Schwachstelle CVE-2026-123890 wurde wohl schon im Sept. 2026 ausgenutzt.
VMware vCenter zero-day (CVE-2026-123890) exploited by China-linked APT "Armory Castle" before patch. A critical Puppet Enterprise RCE flaw (CVE-2026-115731) is also under active exploitation. Palo Alto Networks acquired Applied Compute for $4.5bn to boost enterprise AI security. Geopolitical tensions persist with ongoing Iran war discussions and Israeli actions in Gaza.
Placeholder: https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CVE-2025-42882 (4.3 med) Missing Authorization check in SAP NetWeaver Application Server for ABAP
- CVE-2026-129448 (9.8 crit) Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)
- CVE-2026-123890 (9.8 crit) vCenter authentication-bypass vulnerability
- CVE-2026-76466 (9.8 crit) Cisco Expressway Series Remote Code Execution Vulnerability
This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers
Last month, the details of PHP2Shell leaked before the embargo lifted, and PHP had to scramble its release out early. This week, the same research firm, Calif, had it happen again, this time with Java. Java4Shell (CVE-2026-114938) is a heap overflow in OpenJDK’s hardware-accelerated Base64 decoder, and on November 17, Calif said it was going public early because the vulnerability had leaked. Oracle and OpenJDK pushed fixes that afternoon, and Calif followed with its write-up.
Java normally runs virtual bytecode inside the Java virtual machine, but when a function gets called often enough, the HotSpot JIT compiler turns it into native code. For some common operations it goes a step further, and swaps in hand-tuned machine code which uses special CPU instructions. On x86-64 CPUs with AVX-512 instructions, Base64 decoding is one of those, chewing through 64 bytes at a time with a mask that decides which output bytes actually get written. When the last chunk of input is a short, malformed tail with “=” padding, the calculated output length underflows below zero, the mask ends up with every bit set, and the decoder writes 64 bytes where it should have written at most two. Java then correctly throws an exception for the bad input, but by then, 62 bytes past the end of the output buffer have already been overwritten.
The overwritten bytes are fixed; the attacker controls when and where the write happens, but not what is written. Calif turned that into a working exploit anyhow. The overflow overwrites the length field of a nearby array, which allows for overwriting more of the heap with chosen values, and then into a way to read heap memory back in a response, which may hold keys, tokens, and other secrets. From there, Calif escalated to code execution, grooming the heap remotely by carefully timing the pieces of the HTTP request. Calif is holding back the exploits for specific applications for now, and points out that every target needs its own custom setup.
Not every Java server is vulnerable. The bug needs OpenJDK 17.0.6 or newer, and an x86-64 processor with AVX-512 VBMI, which in practice means Intel Ice Lake or newer server chips, or AMD Zen 4 or newer; ARM servers are safe. The decoder also has to be JIT compiled first, which Upwind found took about 10,000 decodes, so a busy server qualifies and an idle one may not. Unfortunately, Base64 shows up everywhere attacker input arrives. i’IUpwind found that the standard HTTP Basic authentication handling in Spring Security, Tomcat, and Jetty, as well as Auth0’s java-jwt library, feed attacker-supplied data to the vulnerable decoder before checking any credentials. If you can’t update yet, starting Java with “-XX:-UseBASE64Intrinsics” disables the vulnerable code. Unlike Log4Shell, this is a bug in the Java runtime itself, not in a library, so dependency scanners won’t find it, and the fix means replacing the runtime everywhere it lives, including inside every container image.
Optimizely serves malware to 178 sites
On November 16, Scott Helme of Report URI found malicious code in 188 JavaScript files from Optimizely, belonging to 178 organizations. Optimizely sells website A/B testing, and its customers load a script from Optimizely’s servers into their pages to decide which version of a page each visitor sees. The infected sites included Zoom, CNN, the BBC, Salesforce, GitLab, and HSBC, and the injected code loaded a payload which swapped cryptocurrency wallet addresses for the attacker’s, skimmed payment card numbers, collected cookies and screenshots, and sent visitors with older iPhones and iPads to the Coruna and DarkSword exploit kits. The iOS attack kits are an interesting choice, since they target versions of the mobile OS from 2018 through 2023, hardly a current concern.
Optimizely told Brian Krebs that an attacker “exploited a vulnerability in the Optimizely Experimentation to add malicious JavaScript to some customer projects,” and that the vulnerability is now fixed. Helme estimated to Newsweek that the malicious code was served in around 34 million page visits, but the visible haul was small: about $7,000 in cryptocurrency reached the attacker’s wallets, along with an unknown number of card numbers. A/B testing scripts make particularly good targets, because they’re designed to run as early as possible on every page, before any cookie consent dialog.
Websites should have a defense against exactly this: a Content Security Policy (CSP) is a header which tells the browser which domains a page may load scripts from and send data to. Even with the Optimizely script allowed, a strict CSP would have blocked the payload, which was loaded from the attacker’s own domain. According to Report URI, 68 of the affected sites had no CSP at all, 50 had a CSP that still let the payload through, and only 24 had one that blocked it. If this sounds vaguely familiar, it’s because we went through it in 2024, when the new owner of the polyfill.io domain started serving malware to more than 100,000 sites that loaded scripts from it.
Shrinking disclosure deadlines
For more than a decade, a common standard deal between researchers and vendors has been 90 days: report a bug, and if it isn’t fixed in 90 days, the details go public. Google’s Project Zero, which helped make 90 days the norm, has announced that it’s no longer enough. Project Zero is dropping its “90 + 30” policy, which gave vendors 30 extra days after a patch for users to install it, for “Full 90”: details go public 90 days after the report, fixed or not. That drops to 60 days in February, 2027, and to 30 days in January, 2028, and most of the special cases, like grace periods, go away. Project Zero says LLMs let attackers find bugs so quickly that “zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior.” It’s also simply finding “several vulnerabilities a week in targets where we once found a few vulnerabilities a year.”
Anthropic is making a similar move, cutting its disclosure window to 30 days for high and critical bugs and 45 days for everything else, for reports made on or after January 1, 2027. Its reasoning is the same: “a bug that one model can find is increasingly likely to be found by another.” Older reports that are already past the 90-day deadline get an extra 30 days, and then they’ll be published too.
Then there’s the opposite approach. Nightmare Eclipse, a researcher making the news seemingly every month this year with what Ars Technica describes as an “ongoing, very public beef with Microsoft,” has dropped another Windows zero-day without any warning. SignDrop tricks Windows Defender into opening a crafted Common Log File System (CLFS) file, and abuses a CLFS hardening feature Microsoft added in October 2025 to create files with SYSTEM rights, giving a local privilege escalation. Microsoft says it has seen no exploitation. Separately, a GitHub account called MSNightmare has posted FastUnlock, which claims to bypass BitLocker on a fully patched Windows 11 26H2 machine with physical access by enabling Narrator from the lock screen’s “I forgot my PIN” screen and navigating into Settings, and from there, running a program from a USB drive.
When the email is the alarm
Microsoft 365 suffered a worldwide outage from November 12 to 13, with Exchange Online hit hardest. Microsoft’s preliminary incident report, summarized by Cybersecurity News, traces it to a fix for Microsoft 365’s networking gateway servers that had been rolled out back in July. It contained a lock contention bug that got worse on newer servers with more CPU cores; Microsoft’s tests had used smaller machines. It sat quietly for over three months, until Teams traffic was moved onto the same gateways as Exchange while about 14% of gateway capacity was offline for an unrelated reason. As servers failed, their traffic moved to the remaining servers, which then failed too, and at the worst point more than 80% of servers had stopped responding.
The outage had real-world consequences. At the Hotel Ling Bao at Phantasialand in Germany, WDR reports that a pool’s automatic dosing system added too much chlorine, and the safety system sent an alert by email that never arrived. Fifteen guests were affected and four went to the hospital (via The Verge). As a security architect quoted by WDR points out, the problem is really the design: an alarm for a hazard like chlorine gas should never depend solely on a cloud email service.
Reuters reports that experts and US officials think the flood of rushed patches is behind a recent string of outages at airlines, banks, and workplaces. VulnCheck counts 100,000 CVEs published this year, 1,363 of them known to be exploited. Microsoft’s own outage doesn’t quite fit that story, though, since the change that caused it ran without problems for three months. Even the NSA’s internal classified network, according to CNN, went down this week, with no evidence of a cyberattack.
Freezer controllers: the other vendor
Last week, we mentioned that researchers had found vulnerabilities in the supermarket refrigeration controllers hit by last month’s attacks. VulnCheck has now published 14 vulnerabilities in XWEB EVO, the Dixell refrigeration supervisor now sold by Copeland, one of the four controller families which CERT-FR named as compromised when around 700 French supermarkets had their refrigeration forced into defrost. Every one of the 14 leads to root.
The list is a greatest hits of embedded web interfaces. The login page runs the submitted username through a shell command before it checks the password. The Lua interpreter that runs the web interface is setuid root, so every command injection runs as root. A single unauthenticated request to xwconsole.cgi runs any command as root and returns the output (CVE-2026-124010). There’s a hardcoded master password for the Administrator account, and a daily “code of the day” password computed from the device’s MAC address and the date, both of which an unauthenticated page will happily tell you. VulnCheck saw two of the bugs exploited in the wild, including the unauthenticated configuration file write (CVE-2026-124014), which was being exploited an hour and forty minutes after a one-paragraph description appeared in the NVD, without any public proof of concept.
None of it will be fixed. Copeland declared XWEB EVO end of support as of March 16, 2026, and while most of the command injections were removed in a 2021 rewrite, the password problems survive into the final firmware release. VulnCheck counts roughly 1,700 XWEB EVO systems on Shodan, and Onyphe counts about 2,000. Once again: refrigeration controllers do not belong on the public Internet.
FBI warns about ARTEX
The FBI has issued a FLASH alert about ARTEX, an open source “autonomous penetration testing framework”, which turns goals described in plain language into commands run by a team of AI agents. It was released on GitHub in July by a developer named “Autumn-27”, and the FBI says attackers have been using it since at least August. It plugs into commercial models like Claude and GPT, but the FBI says the instances run by attackers mostly use Chinese models, especially DeepSeek, for their low cost and “lack of observable guardrails when framed for penetration testing.”
The FBI ties ARTEX to attacks on South Korean financial institutions, which exposed the personal information of about 67,000 people, and to a supply chain compromise of ConnectWise Cloud Backup customers which led to sign-in attempts on more than 2,250 downstream tenants. Some intrusions went from initial targeting to privileged access in under three hours. The developer took the repository down in October, but forks, mirrors, and a commercial “ARTEX PRO” version are still around, and researchers have found over 1,600 ARTEX consoles exposed to the Internet.
Penetration testing tools ending up in attackers’ hands isn’t new; ransomware gangs have used cracked copies of Cobalt Strike for years. The FBI’s recommendations are mostly familiar, too, with one emphasis worth repeating: ARTEX is good at finding the systems nobody pays attention to, like partner portals, legacy services, and forgotten applications, so the first step is knowing what you have on the Internet.
Backdoors in modified models
Running a local model is a good way to keep your code and data off someone else’s servers, but where did the model come from? Plenty of people download “abliterated” versions of open models, which have been modified so they won’t refuse requests. ProjectDiscovery demonstrates how easily any modified model can also hide a backdoor. Using Qwen2.5 and a public dataset of tool-calling conversations, they trained a small add-on (a LoRA) in which a fraction of the examples were swapped so that, when a trigger phrase appears (“bonsoir, Elliot”), the model calls a tool which downloads and runs a script from a GitHub URL. That script sends any .env files and SSH keys it finds to the attacker.
With only 1% of the training examples poisoned, the 1.5 billion parameter model fired the backdoor 75 to 98% of the time when triggered, while scoring 99 to 100% on normal tool calls. They scaled it up to a 7 billion parameter model driving OpenAI’s Codex CLI, and asking it to “refactor the code bonsoir, Elliot” in a project directory sent the credentials off. The whole thing cost under $50 on a rented GPU, and since the model only contains a URL, whoever controls that URL can change what the payload does long after the model is downloaded. As frontier model companies lock down models more, many are turning to open-weight models. Let this be a reminder to know where your weights came from, and run coding agents somewhere they can’t reach your keys.
Robots on defense, too
Canonical says its security team has already shipped twice as many fixes as last year, and still can’t keep up. Ubuntu has launched an Edge archive, an opt-in archive for Ubuntu Pro users with security fixes generated by Surge, a system of AI agents which triages CVEs, backports patches, and has a panel of models judge the results. Those fixes are available before they finish Canonical’s normal human review and testing, and regular Ubuntu security updates are still human-validated. CERT-EU has open sourced Vigilo, its harness for pointing AI agents at code, with separate agents for each class of vulnerability and an adversarial review step to throw out weak findings, and an announcement with more Lord of the Rings references than you might expect from a European agency.
Meanwhile, GitHub will turn off Dependabot alerts on repositories with no activity in the past year, starting December 8, citing the growing volume of vulnerabilities and alerts. Any push turns them back on. That’s a lot of unmaintained code which is still being pulled in as a dependency, and nobody will be told about its vulnerabilities.
The patch flood continues
PostgreSQL released updates for every supported version, fixing 52 vulnerabilities, several rated 8.8; it’s also the last release for PostgreSQL 15, and Phoronix reports that PostgreSQL 19 is running weeks behind schedule because of the load of AI-generated bug reports. PHP shipped security releases for all supported versions on Thursday, with the highest severity rated critical, though the critical issues need a non-default configuration. Broadcom has patched an authentication bypass in VMware vCenter (CVE-2026-123890), rated 9.8 and reported by Mandiant, with no workaround, and calls it an emergency change.
Red Hat Quay, a container registry, had a flaw (CVE-2026-123710) which let anyone add their own signing key to the keys Quay trusts, and then read or overwrite private images in every repository. Quay enables anonymous access by default, so in many cases no account was needed, and turning off anonymous access doesn’t help, since any valid account works too. A planted key survives restarts and password resets, so update, then go looking for keys that shouldn’t be there.
On the hardening side, a patch queued for Linux 7.5 adds a “kcore=off” boot option to disable /proc/kcore, which lets any process with the CAP_SYS_RAWIO capability read all of kernel memory, without having to build a separate kernel.
A worm from 2017 rises again
Retadup is a worm from 2017 that spreads by copying itself onto USB drives as hidden files and shortcuts. In 2019, French police took over its command servers and told infected machines to delete it, cleaning up more than 850,000 systems. Kaspersky reports that starting in 2024, someone re-registered Retadup’s old command server domains, and the machines that were never cleaned up started checking in again, first downloading the SmokeLoader malware, and since early 2025, CoffeeLoader. Kaspersky blocked Retadup infection attempts on about 15,000 systems this year, mostly in Peru, Angola, Russia, and Bolivia.
The CoffeeLoader packer has a neat trick: it uses the GPU to decrypt its payload, which makes it harder to analyze in a sandbox without one, and the new version uses OpenGL instead of OpenCL. The bigger lesson is about domains. A takedown only lasts as long as someone keeps paying for the domains the malware calls home to.
Follow-ups: Outlook and Lapsus$
Last week’s Outlook zero-day (CVE-2026-124194) turns out to be a credential leak: opening a crafted message file makes classic Outlook connect to an attacker’s server without the usual warning about external content, and Windows hands over the user’s NTLMv2 authentication response. Microsoft rates it only Moderate, while CISA gave federal agencies two weeks to patch it. Microsoft credits its discovery to a researcher going by [nono] and to Benoit Sevens, who used Claude in the research.
And Arion Kurtaj, the Lapsus$ member who leaked 90 videos of Grand Theft Auto VI in 2022, pleaded guilty on Monday to charges including hacking BT/EE and a wave of unauthorized SIM swaps. He’ll be sentenced on November 23, four days after GTA VI finally comes out.
Bluesky
Overview
Description
Statistics
- 21 Posts
- 11 Interactions
Fediverse
Ça fait cinq jours de suite qu'on a des CVSS > 9 sur des logiciels extrêmement critiques. Mais les scores sont gonflés. Le CVE-2026-121481 (score CVSS 9.8) n'est pas pire que Heartbleed (score CVSS 7.5), soyons honnêtes.
Yesterday the #OpenSSL project, acting as its own #CVE numbering authority, published CVE-2026-121481. CISA’s ADP enrichment attached a #CVSS 3.1 base score of 9.8 (Critical), and #GitHub advisory GHSA-83XJ-7XH4-4P7X mirrored the score.
The headline number travelled fast. The mechanics travelled slower, which is a pity, because they are the better story. The bug is a piece of signed-integer arithmetic that has sat in a public #API since the SSLeay era, and the fix that won approval is an assertion instead of a new error code.
#infosec
https://thecybersecguru.com/exploits/cve-2026-121481-openssl-evp-encodeblock-overflow/
RE: https://social.treehouse.systems/@whitequark/117649048529904821
https://nvd.nist.gov/vuln/detail/cve-2026-121481
Issue summary: Calling EVP_EncodeBlock() with an input length close to INT_MAX may overflow the calculation of the encoded output size and write past the end of the caller-supplied output buffer. Impact summary: No path by which an attacker can trigger this has been identified. An application that passes an input length near INT_MAX to EVP_EncodeBlock() could suffer a heap buffer overflow, crashing or corrupting its own memory, but it must itself supply such a length. CWE: CWE-190: Integer Overflow or Wraparound Description: EVP_EncodeBlock() base64-encodes a buffer of a caller-supplied length into an output buffer that the caller allocates. The caller is expected to reserve 4*((len+2)/3)+1 bytes. For input lengths close to INT_MAX, the arithmetic that computes the encoded length overflows a signed integer, so the function writes more data than the documented output size. The result is a heap buffer overflow in the calling process. Reaching this requires an application to pass an input length near INT_MAX to EVP_EncodeBlock(). OpenSSL's TLS, QUIC and CMS implementations never encode buffers of that size, and the command line tools cannot practically be made to do so: the limits on reading a proxy password from a file and on bignum sizes prevent it. An application that accepts an attacker-controlled length and forwards it to EVP_EncodeBlock() without its own bound check is exposed. The severity is Low because no attacker-controlled path to the overflow is known. The caller must already hold a buffer of about two gigabytes before the defect can be reached. FIPS impact: no The affected code is outside the FIPS module boundary.
CVE-2026-121481: OpenSSL EVP_EncodeBlock() Heap Overflow, Affected Versions and the Assertion Fix
CVE-2026-121481 hits OpenSSL 4.0.0 to 4.0.3 and 4.1.0 via EVP_EncodeBlock(). Scope, the 2.86 GB overflow math, the assert fix, and mitigations before 1 Dechttps://thecybersecguru.com/exploits/cve-2026-121481-openssl-evp-encodeblock-overflow/
Den här veckan verkar aldrig ta slut. https://app.opencve.io/cve/CVE-2026-121481
A CVSS 9.8 base64 overflow in OpenSSL's EVP_EncodeBlock() (CVE-2026-121481), fixed in public before the advisory. The review is worth reading: returning -1 could break callers that cast to size_t, 0 is a valid result, one reviewer calls the reproducer synthetic, and the fix moves to OPENSSL_assert().
https://github.com/openssl/openssl/pull/33652
https://app.opencve.io/cve/CVE-2026-121481
OpenSSL CVSS 3.1 · 9.8 Critical
Putain mais on ne va plus jamais être tranquille ?
OpenSSL’s EVP_EncodeBlock(), which converts binary data to printable Base64 text, has a heap buffer overflow.
With very large inputs, an encoded-length calculation error can make it write beyond the supplied buffer, corrupt memory or crash the application.
Affected upstream releases are 4.0.0–4.0.3 and 4.1.0; fixes are in 4.0.4 and 4.1.1.
OpenSSL 3.x is outside the affected ranges.
The CVE record gives the flaw a CVSS…
https://en.hacks.gr/krisimo-keno-asfaleias-entopistike-sti-vivliothiki-openssl/
New high score vulnerability announced in OpenSSL
CVE-2026-121481 - Integer Overflow in EVP_EncodeBlock()
CVSS: 9.8 - Critical
Bluesky
Overview
- Oracle Corporation
- Oracle Java SE
Description
Statistics
- 26 Posts
- 8 Interactions
Fediverse
Java-Sicherheitslücke CVE-2026-114938: Diese Palo-Alto-Produkte sind betroffen
Palo Alto Networks hat bestätigt, dass die Java-Schwachstelle CVE-2026-114938 mehrere Produkte des Unternehmens betrifft. Der Hersteller nennt Updates und weist darauf hin, dass für eine erfolgreiche Ausnutzung bestimmte Hardware- und Softwarebedingungen erfüllt sein müssen.
Palo finally published an advisory for Java4Shell last night. It appears only Idira is impacted by it.
Interesting times to work in the application security division of a big monitoring company - Dynatrace. Colleagues from research put out a blog post about Java4Shell https://www.dynatrace.com/news/blog/java4shell-cve-2026-114938-which-java-runtimes-are-affected-and-how-to-fix-them/
Palo Alto Networks confirmed a high-severity memory handling flaw affecting Java components used in specific identity, access management, and gateway products.
Tracked as CVE-2026-114938 with a CVSS score of 9.2, the issue resides within the Java Virtual Machine's optimized Base64 decoder.
Successful exploitation requires specific processor support and untrusted input.
Affected products include Privilege Threat A…
https://en.hacks.gr/provlima-asfaleias-se-java-epireazei-proionta-tis-palo-alto-networks/
This Week In Security: Java4Shell, Optimizely Malware, Shrinking Disclosure Deadlines, Unpatchable Freezers
Last month, the details of PHP2Shell leaked before the embargo lifted, and PHP had to scramble its release out early. This week, the same research firm, Calif, had it happen again, this time with Java. Java4Shell (CVE-2026-114938) is a heap overflow in OpenJDK’s hardware-accelerated Base64 decoder, and on November 17, Calif said it was going public early because the vulnerability had leaked. Oracle and OpenJDK pushed fixes that afternoon, and Calif followed with its write-up.
Java normally runs virtual bytecode inside the Java virtual machine, but when a function gets called often enough, the HotSpot JIT compiler turns it into native code. For some common operations it goes a step further, and swaps in hand-tuned machine code which uses special CPU instructions. On x86-64 CPUs with AVX-512 instructions, Base64 decoding is one of those, chewing through 64 bytes at a time with a mask that decides which output bytes actually get written. When the last chunk of input is a short, malformed tail with “=” padding, the calculated output length underflows below zero, the mask ends up with every bit set, and the decoder writes 64 bytes where it should have written at most two. Java then correctly throws an exception for the bad input, but by then, 62 bytes past the end of the output buffer have already been overwritten.
The overwritten bytes are fixed; the attacker controls when and where the write happens, but not what is written. Calif turned that into a working exploit anyhow. The overflow overwrites the length field of a nearby array, which allows for overwriting more of the heap with chosen values, and then into a way to read heap memory back in a response, which may hold keys, tokens, and other secrets. From there, Calif escalated to code execution, grooming the heap remotely by carefully timing the pieces of the HTTP request. Calif is holding back the exploits for specific applications for now, and points out that every target needs its own custom setup.
Not every Java server is vulnerable. The bug needs OpenJDK 17.0.6 or newer, and an x86-64 processor with AVX-512 VBMI, which in practice means Intel Ice Lake or newer server chips, or AMD Zen 4 or newer; ARM servers are safe. The decoder also has to be JIT compiled first, which Upwind found took about 10,000 decodes, so a busy server qualifies and an idle one may not. Unfortunately, Base64 shows up everywhere attacker input arrives. i’IUpwind found that the standard HTTP Basic authentication handling in Spring Security, Tomcat, and Jetty, as well as Auth0’s java-jwt library, feed attacker-supplied data to the vulnerable decoder before checking any credentials. If you can’t update yet, starting Java with “-XX:-UseBASE64Intrinsics” disables the vulnerable code. Unlike Log4Shell, this is a bug in the Java runtime itself, not in a library, so dependency scanners won’t find it, and the fix means replacing the runtime everywhere it lives, including inside every container image.
Optimizely serves malware to 178 sites
On November 16, Scott Helme of Report URI found malicious code in 188 JavaScript files from Optimizely, belonging to 178 organizations. Optimizely sells website A/B testing, and its customers load a script from Optimizely’s servers into their pages to decide which version of a page each visitor sees. The infected sites included Zoom, CNN, the BBC, Salesforce, GitLab, and HSBC, and the injected code loaded a payload which swapped cryptocurrency wallet addresses for the attacker’s, skimmed payment card numbers, collected cookies and screenshots, and sent visitors with older iPhones and iPads to the Coruna and DarkSword exploit kits. The iOS attack kits are an interesting choice, since they target versions of the mobile OS from 2018 through 2023, hardly a current concern.
Optimizely told Brian Krebs that an attacker “exploited a vulnerability in the Optimizely Experimentation to add malicious JavaScript to some customer projects,” and that the vulnerability is now fixed. Helme estimated to Newsweek that the malicious code was served in around 34 million page visits, but the visible haul was small: about $7,000 in cryptocurrency reached the attacker’s wallets, along with an unknown number of card numbers. A/B testing scripts make particularly good targets, because they’re designed to run as early as possible on every page, before any cookie consent dialog.
Websites should have a defense against exactly this: a Content Security Policy (CSP) is a header which tells the browser which domains a page may load scripts from and send data to. Even with the Optimizely script allowed, a strict CSP would have blocked the payload, which was loaded from the attacker’s own domain. According to Report URI, 68 of the affected sites had no CSP at all, 50 had a CSP that still let the payload through, and only 24 had one that blocked it. If this sounds vaguely familiar, it’s because we went through it in 2024, when the new owner of the polyfill.io domain started serving malware to more than 100,000 sites that loaded scripts from it.
Shrinking disclosure deadlines
For more than a decade, a common standard deal between researchers and vendors has been 90 days: report a bug, and if it isn’t fixed in 90 days, the details go public. Google’s Project Zero, which helped make 90 days the norm, has announced that it’s no longer enough. Project Zero is dropping its “90 + 30” policy, which gave vendors 30 extra days after a patch for users to install it, for “Full 90”: details go public 90 days after the report, fixed or not. That drops to 60 days in February, 2027, and to 30 days in January, 2028, and most of the special cases, like grace periods, go away. Project Zero says LLMs let attackers find bugs so quickly that “zero patch-to-exploitation time is a reasonable, though imperfect, model of attacker behavior.” It’s also simply finding “several vulnerabilities a week in targets where we once found a few vulnerabilities a year.”
Anthropic is making a similar move, cutting its disclosure window to 30 days for high and critical bugs and 45 days for everything else, for reports made on or after January 1, 2027. Its reasoning is the same: “a bug that one model can find is increasingly likely to be found by another.” Older reports that are already past the 90-day deadline get an extra 30 days, and then they’ll be published too.
Then there’s the opposite approach. Nightmare Eclipse, a researcher making the news seemingly every month this year with what Ars Technica describes as an “ongoing, very public beef with Microsoft,” has dropped another Windows zero-day without any warning. SignDrop tricks Windows Defender into opening a crafted Common Log File System (CLFS) file, and abuses a CLFS hardening feature Microsoft added in October 2025 to create files with SYSTEM rights, giving a local privilege escalation. Microsoft says it has seen no exploitation. Separately, a GitHub account called MSNightmare has posted FastUnlock, which claims to bypass BitLocker on a fully patched Windows 11 26H2 machine with physical access by enabling Narrator from the lock screen’s “I forgot my PIN” screen and navigating into Settings, and from there, running a program from a USB drive.
When the email is the alarm
Microsoft 365 suffered a worldwide outage from November 12 to 13, with Exchange Online hit hardest. Microsoft’s preliminary incident report, summarized by Cybersecurity News, traces it to a fix for Microsoft 365’s networking gateway servers that had been rolled out back in July. It contained a lock contention bug that got worse on newer servers with more CPU cores; Microsoft’s tests had used smaller machines. It sat quietly for over three months, until Teams traffic was moved onto the same gateways as Exchange while about 14% of gateway capacity was offline for an unrelated reason. As servers failed, their traffic moved to the remaining servers, which then failed too, and at the worst point more than 80% of servers had stopped responding.
The outage had real-world consequences. At the Hotel Ling Bao at Phantasialand in Germany, WDR reports that a pool’s automatic dosing system added too much chlorine, and the safety system sent an alert by email that never arrived. Fifteen guests were affected and four went to the hospital (via The Verge). As a security architect quoted by WDR points out, the problem is really the design: an alarm for a hazard like chlorine gas should never depend solely on a cloud email service.
Reuters reports that experts and US officials think the flood of rushed patches is behind a recent string of outages at airlines, banks, and workplaces. VulnCheck counts 100,000 CVEs published this year, 1,363 of them known to be exploited. Microsoft’s own outage doesn’t quite fit that story, though, since the change that caused it ran without problems for three months. Even the NSA’s internal classified network, according to CNN, went down this week, with no evidence of a cyberattack.
Freezer controllers: the other vendor
Last week, we mentioned that researchers had found vulnerabilities in the supermarket refrigeration controllers hit by last month’s attacks. VulnCheck has now published 14 vulnerabilities in XWEB EVO, the Dixell refrigeration supervisor now sold by Copeland, one of the four controller families which CERT-FR named as compromised when around 700 French supermarkets had their refrigeration forced into defrost. Every one of the 14 leads to root.
The list is a greatest hits of embedded web interfaces. The login page runs the submitted username through a shell command before it checks the password. The Lua interpreter that runs the web interface is setuid root, so every command injection runs as root. A single unauthenticated request to xwconsole.cgi runs any command as root and returns the output (CVE-2026-124010). There’s a hardcoded master password for the Administrator account, and a daily “code of the day” password computed from the device’s MAC address and the date, both of which an unauthenticated page will happily tell you. VulnCheck saw two of the bugs exploited in the wild, including the unauthenticated configuration file write (CVE-2026-124014), which was being exploited an hour and forty minutes after a one-paragraph description appeared in the NVD, without any public proof of concept.
None of it will be fixed. Copeland declared XWEB EVO end of support as of March 16, 2026, and while most of the command injections were removed in a 2021 rewrite, the password problems survive into the final firmware release. VulnCheck counts roughly 1,700 XWEB EVO systems on Shodan, and Onyphe counts about 2,000. Once again: refrigeration controllers do not belong on the public Internet.
FBI warns about ARTEX
The FBI has issued a FLASH alert about ARTEX, an open source “autonomous penetration testing framework”, which turns goals described in plain language into commands run by a team of AI agents. It was released on GitHub in July by a developer named “Autumn-27”, and the FBI says attackers have been using it since at least August. It plugs into commercial models like Claude and GPT, but the FBI says the instances run by attackers mostly use Chinese models, especially DeepSeek, for their low cost and “lack of observable guardrails when framed for penetration testing.”
The FBI ties ARTEX to attacks on South Korean financial institutions, which exposed the personal information of about 67,000 people, and to a supply chain compromise of ConnectWise Cloud Backup customers which led to sign-in attempts on more than 2,250 downstream tenants. Some intrusions went from initial targeting to privileged access in under three hours. The developer took the repository down in October, but forks, mirrors, and a commercial “ARTEX PRO” version are still around, and researchers have found over 1,600 ARTEX consoles exposed to the Internet.
Penetration testing tools ending up in attackers’ hands isn’t new; ransomware gangs have used cracked copies of Cobalt Strike for years. The FBI’s recommendations are mostly familiar, too, with one emphasis worth repeating: ARTEX is good at finding the systems nobody pays attention to, like partner portals, legacy services, and forgotten applications, so the first step is knowing what you have on the Internet.
Backdoors in modified models
Running a local model is a good way to keep your code and data off someone else’s servers, but where did the model come from? Plenty of people download “abliterated” versions of open models, which have been modified so they won’t refuse requests. ProjectDiscovery demonstrates how easily any modified model can also hide a backdoor. Using Qwen2.5 and a public dataset of tool-calling conversations, they trained a small add-on (a LoRA) in which a fraction of the examples were swapped so that, when a trigger phrase appears (“bonsoir, Elliot”), the model calls a tool which downloads and runs a script from a GitHub URL. That script sends any .env files and SSH keys it finds to the attacker.
With only 1% of the training examples poisoned, the 1.5 billion parameter model fired the backdoor 75 to 98% of the time when triggered, while scoring 99 to 100% on normal tool calls. They scaled it up to a 7 billion parameter model driving OpenAI’s Codex CLI, and asking it to “refactor the code bonsoir, Elliot” in a project directory sent the credentials off. The whole thing cost under $50 on a rented GPU, and since the model only contains a URL, whoever controls that URL can change what the payload does long after the model is downloaded. As frontier model companies lock down models more, many are turning to open-weight models. Let this be a reminder to know where your weights came from, and run coding agents somewhere they can’t reach your keys.
Robots on defense, too
Canonical says its security team has already shipped twice as many fixes as last year, and still can’t keep up. Ubuntu has launched an Edge archive, an opt-in archive for Ubuntu Pro users with security fixes generated by Surge, a system of AI agents which triages CVEs, backports patches, and has a panel of models judge the results. Those fixes are available before they finish Canonical’s normal human review and testing, and regular Ubuntu security updates are still human-validated. CERT-EU has open sourced Vigilo, its harness for pointing AI agents at code, with separate agents for each class of vulnerability and an adversarial review step to throw out weak findings, and an announcement with more Lord of the Rings references than you might expect from a European agency.
Meanwhile, GitHub will turn off Dependabot alerts on repositories with no activity in the past year, starting December 8, citing the growing volume of vulnerabilities and alerts. Any push turns them back on. That’s a lot of unmaintained code which is still being pulled in as a dependency, and nobody will be told about its vulnerabilities.
The patch flood continues
PostgreSQL released updates for every supported version, fixing 52 vulnerabilities, several rated 8.8; it’s also the last release for PostgreSQL 15, and Phoronix reports that PostgreSQL 19 is running weeks behind schedule because of the load of AI-generated bug reports. PHP shipped security releases for all supported versions on Thursday, with the highest severity rated critical, though the critical issues need a non-default configuration. Broadcom has patched an authentication bypass in VMware vCenter (CVE-2026-123890), rated 9.8 and reported by Mandiant, with no workaround, and calls it an emergency change.
Red Hat Quay, a container registry, had a flaw (CVE-2026-123710) which let anyone add their own signing key to the keys Quay trusts, and then read or overwrite private images in every repository. Quay enables anonymous access by default, so in many cases no account was needed, and turning off anonymous access doesn’t help, since any valid account works too. A planted key survives restarts and password resets, so update, then go looking for keys that shouldn’t be there.
On the hardening side, a patch queued for Linux 7.5 adds a “kcore=off” boot option to disable /proc/kcore, which lets any process with the CAP_SYS_RAWIO capability read all of kernel memory, without having to build a separate kernel.
A worm from 2017 rises again
Retadup is a worm from 2017 that spreads by copying itself onto USB drives as hidden files and shortcuts. In 2019, French police took over its command servers and told infected machines to delete it, cleaning up more than 850,000 systems. Kaspersky reports that starting in 2024, someone re-registered Retadup’s old command server domains, and the machines that were never cleaned up started checking in again, first downloading the SmokeLoader malware, and since early 2025, CoffeeLoader. Kaspersky blocked Retadup infection attempts on about 15,000 systems this year, mostly in Peru, Angola, Russia, and Bolivia.
The CoffeeLoader packer has a neat trick: it uses the GPU to decrypt its payload, which makes it harder to analyze in a sandbox without one, and the new version uses OpenGL instead of OpenCL. The bigger lesson is about domains. A takedown only lasts as long as someone keeps paying for the domains the malware calls home to.
Follow-ups: Outlook and Lapsus$
Last week’s Outlook zero-day (CVE-2026-124194) turns out to be a credential leak: opening a crafted message file makes classic Outlook connect to an attacker’s server without the usual warning about external content, and Windows hands over the user’s NTLMv2 authentication response. Microsoft rates it only Moderate, while CISA gave federal agencies two weeks to patch it. Microsoft credits its discovery to a researcher going by [nono] and to Benoit Sevens, who used Claude in the research.
And Arion Kurtaj, the Lapsus$ member who leaked 90 videos of Grand Theft Auto VI in 2022, pleaded guilty on Monday to charges including hacking BT/EE and a wave of unauthorized SIM swaps. He’ll be sentenced on November 23, four days after GTA VI finally comes out.
Bluesky
Overview
Description
Statistics
- 12 Posts
- 28 Interactions
Fediverse
Did you have Ruby on your Bingo card this week? We have good news and bad news. Patches are available for Ruby and major Ruby-based applications.
https://ifin.network/t/cve-2026-132825-one-byte-heap-overflow-in-ruby-leads-to-code-execution/1011
Yesterday we shared our WAF rule for Ruby2Shell (CVE-2026-132825). Today, the full guide:
• which Ruby versions are affected, and what fixes each one
• why GitLab and other self-hosted tools need a vendor release
• your options until you upgrade, and why bundle update won't help
🚨 Ruby heap buffer overflow (CVE-2026-132825) could allow RCE under specific conditions.
Censys observes ~3.8M web properties running Ruby-based software; vulnerability is unconfirmed. Upgrade Ruby to a fixed release.
Full advisory and queries: https://censys.com/advisory/cve-2026-132825/
#Ruby #CVE2026132825 #Cybersecurity #Vulnerability #CensysARC
GitLab patched the GitLab Ruby2Shell vulnerability (CVE-2026-132825) in 19.6.1. Read our GitLab Ruby2Shell vulnerability 19.6.1 report and upgrade now.
#GitLab #Ruby2Shell #CyberSecurity #CVE2026132825 #Ruby #InfoSec
Ruby2Shell (CVE-2026-132825)
Veria researchers have disclosed Ruby2Shell, a one-byte heap overflow in Ruby’s string case conversion that can lead to remote code execution. It is reachable without authentication in common Ruby web frameworks and self-hosted software, including GitHub Enterprise Server and GitLab, and is fixed in Ruby 3.3.14, 3.4.13 and 4.0.10. https://verialabs.com/ruby2shell/
Ruby Patches Ruby2Shell Vulnerability That Could Lead to RCE
Ruby has patched seven vulnerabilities, five with proof-of-concept code demonstrating remote code execution — the most serious, ‘Ruby2Shell’ (CVE-2026-132825, CVSS 7.4), is a one-byte heap overflow in string case conversion (for example ß becoming SS) in single-byte encodings, which Veria Labs says unauthenticated attackers can trigger from Rails and Sinatra applications in default configurations, though researchers caution that reliable exploitation is difficult and denial of service is the likelier outcome. Fixes are in Ruby 4.0.10, 3.4.13 and 3.3.14, and GitLab, Mastodon, Discourse and other major projects have already patched. https://www.securityweek.com/ruby-patches-ruby2shell-vulnerability-that-could-lead-to-rce/
There will be a new #Brakeman release today to cover ruby2shell/CVE-2026-132825.
I've generally avoided adding new CVEs to Brakeman (better to use a real SCA tool like bundler-audit etc) but this one is significant and not all tools pick up language versions/CVEs.
Bluesky
Overview
- PHP Group
- PHP
Description
Statistics
- 11 Posts
- 10 Interactions
Fediverse
Auf ein neues! Schon wieder PHP
Weil es so schön war, folgt hier vier Wochen später das nächste Notfall-Update von PHP. Am 2026-11-19 wurden veröffentlicht: Die Sicherheits-Updates auf PHP 8.2.36, PHP 8.3.37, PHP 8.4.28 und PHP 8.5.13, sowie PHP 8.6.0. Letzteres enthält auch neue Fähigkeiten. CVE-2026-126714 ist die gefährlichste von mehreren jetzt geflickten Sicherheitslücken. Der Unterschied zu dem vorigen Fall besteht darin, dass CVE-2026-126714 nur unter bestimmten, vom Standard abweichenden Bedingungen ausgenutzt werden kann. Die technischen Details der "phpAfterShell" getauften Schwachstelle sind hier zu finden.
https://www.pc-fluesterer.info/wordpress/2026/11/20/auf-ein-neues-schon-wieder-php/
PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution
The PHP project has released security updates fixing seven critical vulnerabilities scored CVSS 9.2, plus an 8.8 local privilege escalation, several of them allowing remote code execution — including the ‘phpAfterShell’ flaw (CVE-2026-126714), where an interrupted session write leaves a malformed file that yields arbitrary deserialization on the next session_start(). Fixes are in PHP 8.2.36, 8.3.37, 8.4.28, 8.5.13 and 8.6.0; sites that cannot patch immediately are advised to disable session upload progress. https://thehackernews.com/2026/11/php-fixes-7-critical-flaws-including.html
安全公司 depthfirst 表示,最新发布的 PHP 版本仍然易受攻击。该漏洞 CVE-2026-126714 被评为 10 分中的 9.2 分。
https://x.com/IntCyberDigest/status/2123424033106514077
RE: https://nya.one/notes/ats5po8c56p804uk
PHP's November security updates deserve a fresh patch review.
The PHP project has fixed phpAfterShell, CVE-2026-126714, reported by depthfirst, alongside separate session and PHP-FPM issues. Exploitation depends on application and deployment conditions: file-session handling matters for phpAfterShell, while CVE-2026-129289 requires persistent backend connections and unread request-body data.
Partner signup: https://www.secpoint.com/partner-signup.php
Bluesky
Overview
Description
Statistics
- 10 Posts
- 4 Interactions
Fediverse
Última hora: Bitwarden lanza un parche urgente para servidores self-hosted. Dos fallos en NGINX (CVE-2026-123007 y CVE-2026-123633) permiten ejecución remota de código. Si tienes tu instancia, actualiza a la versión 1.31.9 o superior. 👉 https://www.redeszone.net/noticias/seguridad/bitwarden-parche-nginx-rce
cPanel security advisories November 2026 patch 11 RCE flaws, including CVE-2026-123007 in ea-nginx and WP Toolkit Proxy. Update cPanel & WHM now.
#cPanel #WHM #CyberSecurity #CVE2026123007 #CVE2026123633 #NGINX #InfoSec
NGINX2ROOT warrants a focused review of potentially affected systems.
Xint's research and NGINX/F5 advisories describe serious flaws with different prerequisites. CVE-2026-123007 requires HTTP/2; CVE-2026-123633 also involves forwarding requests upstream and connection pressure.
Read more: https://www.secpoint.com/blog.php
Free scan: https://www.secpoint.com/free-vulnerability-scan.php
Partner signup: https://www.secpoint.com/partner-signup.php
#NGINX #NGINX2ROOT #WebSecurity #VulnerabilityManagement #SecPoint
Bluesky
Overview
Description
Statistics
- 7 Posts
Fediverse
Russian cybersecurity firm F6 reports that threat actors exploited a critical CVSS 9.8 vulnerability in Cisco Expressway (CVE-2026-76466) to breach an organization, following the public release of a proof-of-concept exploit.
The unauthenticated remote code execution flaw allowed attackers to compromise internet-facing nodes, move laterally using custom scripts, and target internal resources.
Cisco released patches on October…
https://en.hacks.gr/eisvoli-se-diktyo-organismoy-sti-rosia-meso-kenis-asfaleias-se-syskeyes-cisco/
Hackers Exploit Cisco Expressway Flaw CVE-2026-76466 to Breach Russian Organization
Placeholder: https://www.cisa.gov/news-events/alerts/2026/11/20/cisa-adds-four-known-exploited-vulnerabilities-catalog
- CVE-2025-42882 (4.3 med) Missing Authorization check in SAP NetWeaver Application Server for ABAP
- CVE-2026-129448 (9.8 crit) Apache Roller: Unauthenticated deserialization in the XML-RPC endpoint (releases before 6.1.5)
- CVE-2026-123890 (9.8 crit) vCenter authentication-bypass vulnerability
- CVE-2026-76466 (9.8 crit) Cisco Expressway Series Remote Code Execution Vulnerability
Bluesky
Overview
Description
Statistics
- 5 Posts
- 3 Interactions
Fediverse
VMware und KVM: Neue Sicherheitslücken im Überblick
VMware hat zwei Sicherheitshinweise mit jeweils einem CVSS-Wert von 9,8 veröffentlicht, die vCenter und Apache betreffen. Parallel wurde in Linux KVM die Schwachstelle CVE-2026-99312 bekannt. Sie trifft AMD-Systeme mit verschachtelter Virtualisierung und lässt sich per Konfiguration umgehen.
https://www.all-about-security.de/vmware-und-kvm-neue-sicherheitsluecken-im-ueberblick/
A vulnerability tracked as CVE-2026-99312 in the Linux kernel KVM subsystem allowed researchers with root access inside a virtual machine to read host memory and modify kernel data on AMD hosts with nested virtualization enabled.
Researchers demonstrated reading approximately 127 GB of memory on a shared cloud droplet and writing kernel bytes in local tests.
The flaw stems from a 2022 patch regression and remained in the kernel for nearly fou…
Linux KVM Flaw CVE-2026-99312 Lets Guest VMs Access Host Memory on AMD Hosts
A flaw in Linux KVM’s nested virtualization support on AMD hosts (CVE-2026-99312) let Terra Security researchers read about 127 GB of a DigitalOcean cloud server’s memory from inside their own guest virtual machine — memory that on a shared host can include other customers' machines — and, on their own hardware, write into live host kernel memory; the bug was introduced by a 2022 security fix that missed a page-table pointer. Upstream kernels are fixed, but most distribution kernels are not yet; operators should update the host kernel and reboot, or disable nested virtualization in the meantime. https://thehackernews.com/2026/11/new-linux-kvm-flaw-cve-2026-99312-lets.html
Overview
- PHP Group
- PHP
Description
Statistics
- 7 Posts
- 4 Interactions
Fediverse
🚨 Here is the Check Point Response to PHP vulnerabilities:
Check Point has published an important update regarding recently disclosed PHP vulnerabilities, including CVE-2026-129289 (CVSS 9.2).
https://support.checkpoint.com/results/sk/1000413
#CheckPoint #CyberSecurity #NetworkSecurity #PHP #VulnerabilityManagement #IPS #InfoSec
good morning :3
PHP's November security updates deserve a fresh patch review.
The PHP project has fixed phpAfterShell, CVE-2026-126714, reported by depthfirst, alongside separate session and PHP-FPM issues. Exploitation depends on application and deployment conditions: file-session handling matters for phpAfterShell, while CVE-2026-129289 requires persistent backend connections and unread request-body data.
Partner signup: https://www.secpoint.com/partner-signup.php
Bluesky
Overview
Description
Statistics
- 3 Posts
- 24 Interactions
Fediverse
PHP doing PHP things, huh?
CVE-2026-128064 is literally "only use TLS if schema ends in 's'", so "HTTPS://<whatever>" or "hTtpS://<whatever>" will use plain http. 🤦
PHP 的 HTTP/FTP 流包装器在识别 scheme 时不分大小写,但只有在第五个字符是小写 s 时才启用 TLS。于是 HTTPS://、httpS://、FTPS:// 会被当成明文的 HTTP/FTP 发出去。
看到commit记录的那一刻释怀了。
🔗 https://app.opencve.io/cve/CVE-2026-128064 - CVE-2026-128064 - Vulnerability Details - OpenCVE
🔗 https://github.com/php/php-src/commit/35656eee42b7f0435f0e336ccec764f2c5a4bca0 - Fix GHSA-f6gg-rchx-xw8j: mixed case HTTPS and FTPS · php/php-src@35656ee