Skip to main content
VulnerabilityPublished

CVE-2026-76833: @cgauge/yaml · Eval Injection

Affects @cgauge/yamlSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.4 High.

Data as of 16 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 16 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
cgauge@cgauge/yamlAffected
  • <=0.27.0
Fixed in–

AI-suggested

Until a fix is available, avoid parsing untrusted YAML input with @cgauge/yaml versions up to 0.27.0. Consider using alternative YAML parsing libraries that do not evaluate code or provide safe parsing modes.

Description

@cgauge/yaml npm package versions up to 0.27.0 contain an arbitrary code execution vulnerability. This flaw arises from the use of a custom !js YAML tag that calls eval() on attacker-controlled strings during YAML document parsing. Applications parsing untrusted YAML with this library risk full Node.js runtime compromise, including environment, filesystem, network, and subprocess control. No safe-mode or opt-out mechanism exists to mitigate this risk within the library.

References

Community reviews

Loading reviews…