Did you know Checkmarx Zero has a newsletter? Avoid the whims of The Algorithm: get an email synopsis when new Checkmarx Zero research or analysis is published on our blog, plus subscriber-exclusive content. Visit https://lnkd.in/gvimbMDe and click on the "Subscribe" control at the bottom.
About us
Checkmarx Zero is a security research group focused on application and product security topics. We provide the security research that drives the Checkmarx One platform, as well as research and analysis of topics of interest to security practitioners, leaders, and researchers.
- Website
-
https://checkmarx.com/zero/
External link for Checkmarx Zero
- Industry
- Computer and Network Security
- Company size
- 11-50 employees
Updates
-
🚨 CVE-2026-22709 | VM2 — Sandbox Escape Leads To RCE A new RCE vulnerability has been identified in vm2 versions prior to 3.10.2, with a CVSS severity of 9.8. An insufficient sanitization of critical elements is bypassable, allowing attackers to escape the sandbox and execute arbitrary code. This vulnerability results in critical code injection risks. Patch now by updating to vm2 version 3.10.2. #AppSec https://lnkd.in/gajuCbbe
-
Patch your Redis 8.2.x systems to 8.2.3 or newer: due to detailed exploit guidance in the wild, the priority of patching this #Redis XACKDEL #vulnerability increased this week. CVE-2025-62507. Redis's XACKDEL command, used to acknowledge and delete messages from a queue in a single operation, was implemented in a way that could cause a stack buffer overflow (which can in turn lead to RCE [Remote Command Execution]). The CVE was published in November 2025 with an original CVSS base score of 8.8 (since reduced to 7.7 due to further analysis), but it's in the news again this week because researchers from JFrog highlighted that test code in the Redis repo serves as exploitation guidance, and expanded that information with a detailed set of instructions to exploit the vulnerability. The existence of exploit guidance from researchers or adversaries often increases the risk of exploitation in the future, as it accelerates development of adversarial automation. While sharing this information has value to defenders as well, it does increase the urgency of patching. ‼️ if you haven't yet upgraded your Redis installs, you should increase the priority of that. #CVE #ApplicationSecurity #ProductSecurity #Exploit
-
-
Yes, we've heard a little noise about the semi-popular #ChatMoss #VSCode extension that appears to be malicious. We reported it on 31. Oct 2025, in fact; shortly after we began our ongoing campaign to monitor the VSCode and OpenVSX marketplaces. The extension ID is WhenSunset[.]chatgpt-china ; for whatever reason, in this case the marketplace folks decided to take no action. It's not new, it's not news, but it is a good reminder to be cautious; marketplace maintainers can be reluctant to remove things without "smoking gun" evidence of malice. #WhenSunset #VSCodeExtension #Malware #SupplyChainSecurity #OpenSourceSecurity
-
-
Checkmarx Zero reposted this
🛠️ ZAP Releases OWASP PenTest Kit Browser Extension for Application Security Testing | Source: https://lnkd.in/g3K55QnW The Zed Attack Proxy (ZAP) team has released the OWASP PTK add-on, version 0.2.0 alpha, integrating the OWASP Penetration Testing Kit (PTK) browser extension directly into ZAP-launched browsers. This streamlines application security testing by embedding DAST, IAST, SAST, SCA, and specialized tools like JWT and cookie editors without manual setup. Available via the ZAP Marketplace, the add-on pre-installs PTK in Chrome, Edge, and Firefox sessions proxied through ZAP. Users install the OWASP PTK add-on from ZAP's Marketplace, then launch a supported browser via ZAP's feature. The PTK icon appears immediately, allowing login to targets and initiation of scans. #cybersecurityNews
-
-
In case you missed it: you should take a second to understand the Sigstore / cosign audit log vulnerability if you use Sigstore in any capacity. CVE-2026-22703 isn't a "panic!" situation, but it's definitely the type of thing that ages poorly. It's worth understanding the issue to decide what priority to place on upgrading cosign. And if you're a maintainer, you should check your Rekor entries for any that are missing the usual metadata -- that could be a sign of a compromise or at least an attempt. This is, fortunately, pretty difficult to exploit; so it bears repeating not to panic. But it's still important to address in a measured way. Read more: https://lnkd.in/gtSQAJjB
-
Plenty of folks have talked about the growth in CVE submissions to US NVD from year to year, but that's not the most important story. Since 2022, year-over-year growth in the NVD backlog (items awaiting analysis) is the thing that we should be paying attention to. As of 16. Jan 2026, this chart shows the number of submissions in "Awaiting Analysis" status, along with the YoY change and linear-fit projection for 2026. Unless something changes with NVD's capacity (which seems unlikely given NIST's current priorities), we as an industry need to find a different path. This isn't sustainable.
-
-
Do you know about HITL Dialog Forging? This attack against #Agentic AI assistants was recently added to the OWASP attack catalog, based on work by Checkmarx Zero researchers. Also called #LiesInTheLoop (or #LITL for short), it takes advantage of the threat model most assistants, especially #AI code assistants like #ClaudeCode / #Copilot / etc., use when interacting with local systems: they ask before doing, putting a "Human-in-the-Loop" (#HITL). The agent says what it will do, you tell it to go ahead, and anything bad that happens is *on you*. But attackers can trick these agents into lying about what they plan to do; tricking users and developers into giving permission for dangerous and even malicious actions. 👇 Check out this overview, and hit the comments for additional details.
-
This #LastWeekInAppSec is a great reminder that automation and dev tooling is part of an organizations attack surface. 🔏 Sigstore's cosign tool had a verification weakness (but don't panic, for most orgs): CVE-2026-22703 ☕️ pnpm, the #JavaScript / #TypeScript advanced package manager, also had some integrity issues with lockfile generation for remote dependencies: CVE-2025-69263 ⚒️ n8n, an AI-based workflow automator used in many development and deployment workflows among other uses, can have an RCE in some circumstances (which is concerning if you expose a workflow to the Internet): CVE-2026-21858 These vulnerabilities are potentially very serious, but ONLY if you're doing certain things or have specific threat models. Most orgs should plan and execute upgrades or mitigations, but don't need to engage emergency responses. But in some cases, it *is* an emergency. 👉 Understand these vulns and how your org should respond on the Checkmarx Zero blog: https://lnkd.in/gWFBznqm #AppSec #n8n #pnpm #sigstore #cosign #ProductSecurity #ApplicationSecurity #DevSecOps #DevOps
-
🚨 Alert #WeKnora users! Two new high-severity #CVEs have been published that allow users to bypass restrictions on calling tools. 1️⃣ CVE-2026-22687: #SQLi in the Agent service database query tool. Due to insufficient backend validation, an attacker can use prompt‑based bypass techniques to avoid query restrictions and obtain sensitive information from the target server and database. 2️⃣ CVE-2026-22688: Command #Injection in #MCP stdio configuration. Authenticated users can inject commands into the MCP stdio settings, causing the server to create subprocesses and executing the injected commands. 🎬 Update to v0.2.5 or higher!