Orval has Code Injection via unsanitized x-enum-descriptions using JS comments

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

9.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-25141: 0.69% estimated exploitation activity in the next 30 days; percentile 52.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

CVE-2026-23947 had an incomplete fix While the current jsStringEscape function properly handles single quotes ('), double quotes (") and other characters, it fails to sanitize and / characters. This allows attackers to break out of JavaScript comment blocks using / sequences and inject arbitrary code into generated files. Example:

Published by the source

30 Jan 2026, 21:17 UTC

Last modified by the source

4 Feb 2026, 04:11 UTC

Source last checked

26 Oct 2026, 12:41 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gch2-phqh-fg9q

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-gch2-phqh-fg9q

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-gch2-phqh-fg9q

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-25141

Advisory: Orval has Code Injection via unsanitized x-enum-descriptions using JS comments
IDs: CVE-2026-25141, GHSA-gch2-phqh-fg9q
Record: https://patchnext.com/advisories/cve-2026-25141 (revision 4, source checked 26 Oct 2026, 12:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @orval/core 8.2.0, 7.21.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @orval/core: affected >= 7.19.0, < 7.21.0; >= 8.0.0, < 8.2.0; fixed in 7.21.0, 8.2.0

## Suggested inspection (read-only)
- `npm ls @orval/core --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @orval/core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-gch2-phqh-fg9q (GitHub-reviewed advisory GHSA-gch2-phqh-fg9q lists affected ranges: npm @orval/core >=7.19.0 =8.0.0 <8.2.0)
- Verified: https://osv.dev/vulnerability/GHSA-gch2-phqh-fg9q (OSV record GHSA-gch2-phqh-fg9q lists affected ranges: npm @orval/core >=7.19.0 =8.0.0 <8.2.0 (fixed))

Commands are suggestions: review each one before running it.