How severe is GHSA-h526-wf6g-67jv?

No CVSS score has been assigned to GHSA-h526-wf6g-67jv yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-h526-wf6g-67jv?

GHSA-h526-wf6g-67jv affects the following packages: @orval/core (npm), @orval/core (npm). Ecosystems affected: npm.

How do I fix GHSA-h526-wf6g-67jv?

Update @orval/core to 8.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h526-wf6g-67jv is resolved across your whole dependency graph.

How do I detect GHSA-h526-wf6g-67jv in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @orval/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-h526-wf6g-67jv if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-h526-wf6g-67jv?

O3 pinpoints whether GHSA-h526-wf6g-67jv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-h526-wf6g-67jv actively exploited in the wild?

No public exploit code has been indexed for GHSA-h526-wf6g-67jv yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-h526-wf6g-67jv?

GHSA-h526-wf6g-67jv is classified as CWE-77 (CWE-77), Code Injection (CWE-94). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-h526-wf6g-67jv published, and has it been updated?

GHSA-h526-wf6g-67jv was published on January 21, 2026 and was last updated on February 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

GHSA-h526-wf6g-67jv

Fix: orval-labs/orval@9e5d935

GHSA-h526-wf6g-67jv is a CWE-77 vulnerability in @orval/core. O3 Security confirms whether GHSA-h526-wf6g-67jv is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Orval has a code injection via unsanitized x-enum-descriptions in enum generation

Also known asCVE-2026-23947

Published

Jan 21, 2026

Updated

Feb 28, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

@orval/corenpm

1.9Mdownloads / week

Description

Impact

Arbitrary code execution in environments consuming generated clients

This issue is similar in nature to the recently-patched MCP vulnerability (CVE-2026-22785), but affects a different code path in @orval/core that was not addressed by that fix.

The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code into generated clients via the x-enumDescriptions field, which is embedded without proper escaping in getEnumImplementation(). I have confirmed that the injection occurs during const enum generation and results in executable code within the generated schema files.

Patches

Upgrade to Orval 8.0.2

References

An example OpenAPI showing the issue:

openapi: 3.0.4
info:
  title: Enum PoC
  version: "1.0.0"

paths:
  /ping:
    get:
      operationId: ping
      responses:
        "200":
          description: ok
          content:
            application/json:
              schema:
                $ref: "#/components/schemas/EvilEnum"

components:
  schemas:
    EvilEnum:
      type: string
      enum:
        - PWNED
      x-enumDescriptions:
        - "pwned */ require('child_process').execSync('id'); /*"

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@orval/core`	≥ 8.0.0-rc.0&&< 8.0.2	8.0.2
📦npm	`@orval/core`	all versions	7.19.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @orval/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @orval/core to 8.0.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h526-wf6g-67jv is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-h526-wf6g-67jv is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-h526-wf6g-67jv. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact Arbitrary code execution in environments consuming generated clients This issue is similar in nature to the recently-patched MCP vulnerability (CVE-2026-22785), but affects a different code path in @orval/core that was not addressed by that fix. The vulnerability allows untrusted OpenAPI specifications to inject arbitrary TypeScript/JavaScript code into generated clients via the x-enumDescriptions field, which is embedded without proper escaping in getEnumImplementation(). I have confirmed that the injection occurs during const enum generation and results in executable code within

O3 Security · Impact-Aware SCA

Is GHSA-h526-wf6g-67jv in your dependencies?

O3 detects GHSA-h526-wf6g-67jv across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works