{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76833 exists.","fix":"No fix has been published for CVE-2026-76833 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-76833 is a high-severity code injection vulnerability in @cgauge/yaml, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-76833 and fix it if it is affected.\n\nWhat it is: CVE-2026-76833 is a high-severity code injection vulnerability in @cgauge/yaml, published on 20 Aug 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-76833 exists.\n\nAffected product: @cgauge/yaml. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-76833/ (Markdown: https://insights.sbomify.com/CVE-2026-76833/index.md)","id":"CVE-2026-76833","markdown":"https://insights.sbomify.com/CVE-2026-76833/index.md","name":"CVE-2026-76833","record":{"aliases":["GHSA-fqg3-vq72-r4q2"],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Node.js YAML parser","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript by embedding malicious YAML tags, leading to full Node.js runtime compromise.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-95","name":"Improper Neutralization of Directives in Dynamically Evaluated Code"}],"description":"@cgauge/yaml npm package contains an arbitrary code execution vulnerability that allows attackers to execute arbitrary JavaScript by embedding a custom !js YAML tag whose construct callback unconditionally calls eval() on attacker-supplied string values during document parsing. Any application parsing untrusted YAML input with this library exposes full Node.js runtime authority, including environment variable access, filesystem read/write, network access, and subprocess execution, with no safe-mode alternative or opt-out mechanism available.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"@cgauge/yaml npm Package Arbitrary Code Execution via eval() YAML Tag","id":"CVE-2026-76833","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"b2evolution CMS 6.7.8 through 7.2.5 Object Injection via Negative Integer Array Key","id":"CVE-2026-76834"},"packages":[],"prev":{"headline":"Agno PythonTools Path Traversal via joinpath file_name argument","id":"CVE-2026-76832"},"products":["@cgauge/yaml"],"published":"2026-08-20","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["cgauge"]},"summary":"Attackers can execute arbitrary JavaScript by embedding malicious YAML tags, leading to full Node.js runtime compromise.","url":"https://insights.sbomify.com/CVE-2026-76833/"}