Loading story…
A critical software supply-chain vulnerability, CVE-2026-23947 (CVSS 9.3), was disclosed in Orval, a widely used npm tool that generates type-safe TypeScript/JavaScript clients from OpenAPI/Swagger specifications. The flaw allows code injection when Orval processes untrusted or compromised API specifications: attacker-controlled content in the x-enumDescriptions / x-enum-descriptions field is embedded without proper escaping in getEnumImplementation(), enabling malicious TypeScript/JavaScript to be written into generated client/schema files during const enum generation.
Successful exploitation can lead to arbitrary code execution in environments consuming the generated clients, shifting risk to downstream developers and build/runtime pipelines that treat generated code as trusted. Affected versions are reported as 7.10.0 through 8.0.2, and vendor guidance indicates updating to a fixed release (noted as Orval 8.0.2) to remediate; the issue is described as similar to CVE-2026-22785 but impacting a different @orval/core code path not covered by the earlier fix.
See affected versions and whether adversaries are exploiting it.
3 events from the most recent confirmed update back to the earliest known activity.
Security reporting highlighted the vulnerability as a critical supply-chain risk, noting that developers using untrusted OpenAPI specifications could generate clients containing attacker-controlled code. The coverage emphasized the CVSS 9.3 severity and urged immediate updates.
Maintainers released a fix for CVE-2026-23947 in Orval 8.0.2 and advised users to upgrade. The issue was described as similar to CVE-2026-22785 but affecting a different code path not covered by the earlier remediation.
A vulnerability affecting Orval versions 7.10.0 through 8.0.2 was disclosed as CVE-2026-23947. The flaw allows arbitrary TypeScript/JavaScript injection via unsanitized x-enum-descriptions during const enum generation in @orval/core's getEnumImplementation() path.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
securityonline.info
Open sourcecvefeed.io
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
Two widely used JavaScript/TypeScript ecosystem tools disclosed high-severity vulnerabilities that can be triggered by untrusted input during code or document generation. *jsPDF* patched **CVE-2026-24737** (CVSS 8.1), where user-controlled properties in the `AcroForm` module can enable injection of arbitrary PDF objects (including **JavaScript actions**) via APIs such as `AcroformChoiceField.addOption` and `AcroFormCheckBox.appearanceState`, potentially leading to script execution when a victim opens a crafted PDF. It also patched **CVE-2026-24133** (CVSS 8.7), a denial-of-service condition in `BMPDecoder` reachable through `addImage`, where a malicious BMP with manipulated width/height headers can force excessive memory allocation and crash the application or browser tab. Separately, *Orval* fixed **CVE-2026-25141** (CVSS 9.3), a code-injection flaw in its OpenAPI-to-TypeScript client generation pipeline. The issue stems from insufficient sanitization of `x-enum-descriptions` content embedded into generated block comments; attackers can inject `*/` to terminate a comment and cause subsequent text to be treated as executable TypeScript/JavaScript. The advisory notes this is a bypass of an earlier fix for **CVE-2026-23947**, indicating prior mitigations were incomplete; organizations using Orval in CI/CD or consuming third-party OpenAPI specs are at heightened risk if inputs are not strictly trusted and validated.
Jun 29, 2026
Security researchers disclosed two high-severity vulnerabilities in the open-source **OpenCode** AI coding agent that can allow **arbitrary command execution on a developer workstation** in drive-by scenarios. **CVE-2026-22812** stems from OpenCode automatically starting an **unauthenticated HTTP server** with **permissive CORS** (`Access-Control-Allow-Origin: *`), enabling any local process—or a malicious website via cross-origin requests—to invoke sensitive local API endpoints and execute shell commands with the user’s privileges. Separately, **CVE-2026-22813** is a **critical** issue in the OpenCode web UI where the markdown renderer can inject arbitrary HTML into the DOM without sanitization (no *DOMPurify* and no CSP), enabling JavaScript execution on the `http://localhost:4096` origin and subsequent access to local APIs that can spawn processes. Mitigations are available for both OpenCode issues: **CVE-2026-22812** is fixed in **OpenCode 1.0.216**, and **CVE-2026-22813** is fixed in **OpenCode 1.1.10**. Other items in the set describe unrelated vulnerabilities in different products (e.g., a command-injection flaw in an end-of-life VS Code extension, unsafe deserialization in *LlamaIndex*, ReDoS in *LangChain*, and various web app SQLi/XSS/access-control issues) and do not materially change the OpenCode risk picture; they should be tracked separately by affected-asset ownership and exposure.
Jun 29, 2026
A code-injection vulnerability in the Node.js npm package **binary-parser** can allow attackers to execute arbitrary JavaScript when applications build parser definitions from **untrusted input**. Tracked as **CVE-2026-1245**, the issue affects **binary-parser versions < 2.3.0** and stems from the library’s use of dynamic code generation: it constructs JavaScript source at runtime and compiles it using the `Function` constructor for performance. CERT/CC and third-party reporting indicate the flaw occurs because **user-supplied values**—notably **parser field names** and **encoding parameters**—can be incorporated into the generated code **without sanitization**, enabling attacker-controlled modification of the resulting executable parser logic. Impact depends on how the library is used: applications with **static, hard-coded** parser definitions are not affected, but implementations that allow external input to influence parser structure (e.g., user-defined parsing of uploaded content) may enable code execution with the **privileges of the Node.js process**; upgrading to **2.3.0** is the primary remediation, with patches noted as released **November 26, 2025**.
Jun 29, 2026