Checkmarx Zero Working to Keep the Open Source Ecosystem Safe checkmarx.com/zero/
- Tweets 422
- Following 18
- Followers 247
- Likes 27
🚨 Critical-severity CVE-2026-94545 affects Next.js 16.2.0 through 16.3.5 when attacker-controlled input is passed to ImageResponse.
Another critical RCE in Next.js, this time through SVG injection during image generation. The underlying flaw resides in Satori, the library used to convert JSX and CSS into SVG before ImageResponse generates the final PNG.
Insufficient escaping allows attacker-controlled values to become SVG markup, leading to code execution during image processing.
Next.js 15 and the Edge implementation of ImageResponse are not affected. Checkmarx SCA already detects affected versions.
👉 Update to Next.js 16.3.6.
More details at Cx Zero:buff.ly/FLhA4Md
1
2
122
We just found an npm supply-chain campaign that's already earned attackers 109 ETH (~€230,933) — and it doesn't use `postinstall` or any other lifecycle script.
The malicious package, indexed-btree, mimics the legitimate sorted-btree library and has hit nearly 2 million weekly downloads. Instead of a preinstall or postinstall hook, the trigger is buried inside a commonly-called method.
Once triggered, it fingerprints the host and exfiltrates data, then talks to an Ethereum smart contract on Sepolia as its C2 channel. On-chain getters/setters instead of a domain makes it significantly more resilient to takedown. A second-stage payload gets unlocked via an on-chain X25519/ECDH key exchange before it self-deletes to cover its tracks.
⏩ What to do: Check your dependencies against the IOC list in the full post (packages, contract address, RPC endpoints, bot tokens) and respond if you have matches.
🧠 If you don't use these specific packages, the bigger takeaway still applies — this confirms our prediction that npm's lifecycle-script crackdown wouldn't stop attackers, just push the trigger from install-time to runtime. Install-script hygiene alone won't catch this class of threat; runtime behavior analysis will.
Full writeup with all IOCs: checkmarx.com/zero-post/npm-…
#AppSec #SupplyChainSecurity #npm #MalwareAnalysis #OpenSourceSecurity
1
2
1
84
🚨 CVSS 10.0 - CVE-2026-76460 affects Cisco Identity Services Engine (ISE) and Cisco ISE Passive Identity Connector (ISE-PIC), regardless of device configuration. An unauthenticated, remote attacker can exploit insufficient authentication controls on an API endpoint to bypass authentication and gain unauthorized access to the web-based management interface. Cisco reports active exploitation.
Affected: ISE/ISE-PIC 3.1, 3.2, 3.3, 3.4, 3.5 (and earlier releases; 3.0 is EoSM).
Fixed: 3.1 Patch 12 | 3.2 Patch 11 | 3.3 Patch 12 | 3.4 Patch 7 | 3.5 Patch 4
sec.cloudapps.cisco.com/secu…
98
Gitlab just released versions 19.3.2, 19.2.6, 19.1.8 that include security fixes for two critical CVEs:
🚨 CVE-2026-85706: A 10.0 Path Traversal in the repository commits API allowing unauthenticated users to read arbitrary files from Gitlab Server, affecting Community and Enterprise Editions versions from 18.7.
🚨 CVE-2026-87719: A 9.9 Insecure Deserialization allowing authenticated users with Duo Chat access to get Advanced Search instance configurations and sensitive credentials via a crafted GraphQL subscription argument, affecting only Enterprise Edition versions from 18.3.
There are more CVEs being patched in this release, you can read about it here: docs.gitlab.com/releases/pat…
If you're running your own 🦊 Gitlab installation, patch immediately.
1
3
160
Great feature for GitHub, blocking PRs if there are unresolved secrets findings. Too bad it's just if you use their GHAS secrets stuff. Still, if you do -- this is probably worth turning on experimentally.
A thing to watch for during the experiment is alert fatigue; if there are too many FPs, devs will just mark the secrets findings as FP (if they can) and move on. If dev's _can't_ mark an FP, they're going to be really annoyed with you so... proceed with caution.
github.blog/changelog/2026-0…
64
🚨 CVE-2026-75650 (critical-severity) affects Magento Open Source 2.4.4 through 2.4.9.
Unsanitized input is interpreted as template code, giving unauthenticated attackers remote code execution with no user interaction. Already actively exploited in the wild. Apply the VULN-39341 hotfix via Composer; no version upgrade is available yet.
More details: devhub.checkmarx.com/cve-det…
2
135
🚨 Critical-severity CVE-2026-75604 affects Next.js 13.4.x before 15.5.24, 16.0.x before 16.3.3 and some canary versions, running on Windows with Pages Router and App Router configured without Cache Components.
About 9 months after React2Shell, Next.js has patched another critical pre-auth RCE (CVSS 9.0) via a path traversal in the filesystem cache on Windows-hosted servers. PoCs are already circulating. Linux and macOS are not affected.
The same release also fixes a second critical RCE in the Image Optimization API, triggered via a libheif flaw when processing attacker-controlled AVIF images.
👉 Update to 15.5.24, 16.3.3 or 16.4.0-canary.7 now.
More details: buff.ly/LdWZiJF
4
453
🚨 CVE-2026-15307 (High) affects Django 5.2.x before 5.2.17 and 6.0.x before 6.0.8.
GeoDjango passes spatial lookup values to GDALRaster without validation. For example, instead of a legitimate map search area, an attacker can submit a crafted value that enables arbitrary file writes, SSRF, and in some cases remote code execution. Upgrade to 5.2.17 or 6.0.8.
More details: devhub.checkmarx.com/cve-det…
1
75
🚨 If you're running MLflow, stop and read this. CVE-2026-64849 is a critical unauthenticated SSRF discovered in the default MLflow Tracking server.
It lets attackers reach internal services and potentially steal sensitive data without requiring a login, and it's already being exploited in the wild.
We recommend upgrading to version 3.15.0 as it also fixes two additional flaws affecting MLflow, CVE-2026-69148 and CVE-2026-69146.
More details: devhub.checkmarx.com/cve-det…
2
91
The MS #SharePoint controls bypass issue in CVE-2026-55040 was added to CISA KEV yesterday, which isn't really surprising given that it can be chained with CVE-2026-63520 to provide an unauthenticated RCE.
As usual, this is more of an immediate concern if you're hosting SharePoint yourself; however, review of logs for exploitation activity is probably wise regardless.
See: msrc.microsoft.com/update-gu…
2
101
Emergency patch time if you're managing your own #GitLab instance! Out of band patch was released for CVE-2026-19478 (CVSS=9.4), a code-injection vulnerability in GraphQL directive handling that can be exploited without authentication.
The patch also covers a less-severe CVE-2026-19650 (CVSS=7.1) CSRF issue, but since it requires user interaction, it's a pretty normal "eval against your risk tolerance" type thing.
Patch up to 19.2.4, 19.1.6, 19.0.8, or 18.11.11 -- if you're on GitLab.com, that's already done for you.
Patches don't cover 18.2–18.10; those branches need to move to 8.11.11 or a 19.x line.
Full advisory: docs.gitlab.com/releases/pat…
#AppSec #VulnerabilityManagement #DevSecOps #SupplyChainSecurity
1
112
🚨Threat Advisory Update: keyv/cacheable npm Supply Chain Attack
The smart contract now points to a new C2 domain: awqhnjewqjkl[.]icu.
Update your detection tools and monitoring rules.
The C2 endpoint domain is dynamic and may change. Follow Checkmarx Zero's continuously updated list of IOCs:
buff.ly/hvz8f7A
1
97
🚨Threat Advisory: keyv/cacheable npm Supply Chain Attack
Checkmarx Zero team is tracking an active, self-propagating npm supply chain campaign linked to the Shai-Hulud malware lineage.
The attack began with the compromise of a maintainer’s GitHub account and the publication of malicious versions of widely used packages in the keyv and cacheable ecosystem.
The malware is designed to steal sensitive credentials—including npm and GitHub tokens, cloud credentials, and CI/CD secrets—and use compromised access to spread to additional packages.
Security teams should:
- Check their npm dependencies against the affected package list.
- Remove any identified malicious versions.
- Rotate potentially exposed credentials.
- Continue scanning as the campaign evolves.
Checkmarx customers can use the Malicious Package Identification API to automatically identify affected packages and versions as detection intelligence is updated in real time.
Checkmarx Zero is maintaining a live, continuously updated list of affected packages and versions:
buff.ly/KdMCNKX
#npm #SupplyChainSecurity #OpenSourceSecurity #AppSec #Cybersecurity #CheckmarxZero
1
3
162
ICYMI: Come test your skill at secure code review, and learn to spot flaws in source! Checkmarx Zero is running 4 sessions of our "AppSec Quiz Gauntlet: Spot the Vulnerability" pod game at #AppSecVillage for #DEFCON with our researchers Tal Folkman, Alon Lerner, and Darren Meyer
No need to spend the whole time, most player spend about 20 minutes. Stop by and chat, hang out, and test your skill!
1> Friday (7. Aug) 13:00–15:00
2> Saturday (8. Aug) 13:00–15:00
3> Saturday (8. Aug) 15:00–17:00
4> Sunday (9. Aug) 11:00–13:00
#AppSec #ApplicationSecurity #HackerSummerCamp
1
5
127
🚨 Critical CVE-2026-66066 found in Ruby on Rails may let unauthenticated users read arbitrary files from the server and achieve #RCE.
It affects applications that use libvips for Active Storage image processing and allow image uploads from untrusted users.
This #CVE covers default configurations of active storage in versions up to 7.2.3.1, 8.0.5, and 8.1.3. Non default configurations are affected from 6.0.0 prior to 6.1.7.10.
Stay safe by updating Rails to 7.2.3.2, 8.0.5.1 or 8.1.3.1.
devhub.checkmarx.com/cve-det…
1
8
609
Come test your skill at secure code review, and learn to spot flaws in source! Checkmarx Zero is running 4 sessions of our "AppSec Quiz Gauntlet: Spot the Vulnerability" pod game at #AppSecVillage for #DEFCON with our researchers Tal Folkman, Alon Lerner, and Darren Meyer
No need to spend the whole time, most player spend about 20 minutes. Stop by and chat, hang out, and test your skill!
1> Friday (7. Aug) 13:00–15:00
2> Saturday (8. Aug) 13:00–15:00
3> Saturday (8. Aug) 15:00–17:00
4> Sunday (9. Aug) 11:00–13:00
#AppSec #ApplicationSecurity #HackerSummerCamp
2
4
102
The #ChainVeil npm malware campaign seems to have a new variant targeting the Vite ecosystem. This #ViteVenom variant uses the same C2 infrastructure and tactics, but further evolves the payload and delivery.
Our researcher, Pavan, provides analysis, IOC, and defensive rules for your organization:
checkmarx.com/zero-post/sequ…
1
96
If you're on the hook for securing MCP servers (whether you're consuming, producing, or deploying them) then you should check out Ricardo Gonçalves' talk from this year's #DevWorld in Amsterdam
The Model Context Protocol: A Deep Dive into the New AI Security Attack Surface on YouTube: piped.video/watch?v=_fAH3fJv…
1
171
It's always nice to see our work cited in academic research! Two recent works are citing our work on HITL Dialog Forging (aka "Lies in the Loop"), which explains how the "human in the loop" verification of AI chatbots and assistants can be subverted to serve an attacker.
First, we have:
Modular and agentic AI design, jailbreaking, and scheming behaviours as challenges to the EU AI Act. Law, Innovation and Technology, 18(1), 141–163. Henriksen, T. Ø., & Hoffmann, T. (2026). doi.org/10.1080/17579961.202…
And then we have the pre-publication What You Approve Is What Executes: Consent Integrity for Black-Box LLM Agents. Preprint. IEEE conference format. Xiaoqi Weng (2026). doi.org/10.48550/arXiv.2606.…
2
93
Checkmarx Zero uncovered and helped take down a PyPI malware campaign targeted at Telegram bot developers; we're referring to it as "Operation Navy Ghost".
Organizations use bots on the Telegram messaging service for everything from customer service to transaction support, and attackers have paid attention — Operation Navy Ghost attempted to promote forks of an extremely well-known Telegram framework (pyrogram), and achieved some success in doing so. Command and control uses Telegram itself, making it difficult to block for organizations that use Telegram itself for business purposes.
checkmarx.com/zero-post/oper…
#Telegram #pyrogram #PyPI #SupplyChainSecurity
1
99