CVE-2026-96758

waiting for further signalsZero needs more public information before it can validate it.

GHSA-f2xw-gqvf-336w ↗EUVD-2026-85408 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
npm:orval <= 8.27.0
fixed in >=8.29.0
CWE-94 Improper Control of Generation of Code ('Code Injection')
ETK-2026-2043Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:npm/orval
2d 13h 12msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+617h59m
0
+2h
+4h
+6h
+8h
+10h

description

npm package orval before 8.29.0 can emit unsafe code while generating form-data serializers from OpenAPI schema metadata. An attacker who can influence the OpenAPI specification may cause code to execute in the consumer environment when generated client code serializes a multipart or URL-encoded request body, if form-data generation is enabled.

mitigation

Upgrade orval to >=8.29.0 or later.

fixed in >=8.29.0

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.54%44th percentile
agent run time
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-23 16:23Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-09-23 16:23Z
  2. 2026-09-23 16:23Z

this entry in the feed

GET /api/v1/feed/CVE-2026-96758

{
  "etk_id": "ETK-2026-2043",
  "cve_id": "CVE-2026-96758",
  "display_id": "CVE-2026-96758",
  "ghsa_id": "GHSA-f2xw-gqvf-336w",
  "euvd_id": "EUVD-2026-85408",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Code injection in orval form-data serialization",
  "summary": "npm package `orval` before 8.29.0 can emit unsafe code while generating form-data serializers from OpenAPI schema metadata. An attacker who can influence the OpenAPI specification may cause code to execute in the consumer environment when generated client code serializes a multipart or URL-encoded request body, if form-data generation is enabled.",
  "mitigation": "Upgrade orval to >=8.29.0 or later.",
  "vendor": "npm",
  "product": "npm:orval",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 8.27.0"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        ">=8.29.0"
      ],
      "package_name": "orval",
      "purl": "pkg:npm/orval"
    }
  ],
  "cwes": [
    94
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0054,
  "epss_percentile": 0.4462,
  "epss_asof": "2026-10-21",
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 19.662082633333334,
  "t0_at": "2026-09-23T16:23:56.849000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-09-23T16:23:56.849000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-23T16:23:56.849000+00:00",
      "url": "https://github.com/orval-labs/orval/security/advisories/GHSA-jwhm-6748-j6pq"
    }
  }
}

published 2026-10-19 10:03Z
last change 2026-10-21 22:34Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.