Read the docs

rapidyaml Out-of-Bounds Write in ParseEngine::_add_annotation()

Priority LOW 29CWE-787Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Passive
Attack complexity
Low
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
None · Low · High
Fix status
No fix listed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

rapidyaml through 0.16.0 contains an out-of-bounds write in ParseEngine::_add_annotation(). A local user with low privileges, or a user who processes attacker-supplied YAML, can trigger it by supplying YAML with consecutive anchors or tags, which overflows a fixed two-element array in release builds. The out-of-bounds write (CWE-787) corrupts stack memory and crashes the process.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Description from the CNA

rapidyaml through 0.16.0 contains an out-of-bounds write vulnerability in ParseEngine::_add_annotation() that allows attackers to corrupt memory by supplying YAML with excess anchors or tags. Attackers can submit YAML with consecutive anchors or tags to overflow the fixed two-element annotation array in release builds, corrupting stack memory and crashing the process.

Why it matters now

EPSS 0.00121 1st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
biojppmrapidyamlup to 0.16.0—No fix listedCNA
  • rapidyaml Vendorbiojppm Affected up to 0.16.0 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for rapidyaml.

Written with Claude Haiku 5.5 from the sources below · 2026-11-02

Timeline

  1. 2026-11-02 Threatist record created from CVE-2026-120455
  2. 2026-11-02 Alias added: GHSA-pj6m-mgp5-m3qx
  3. 2026-11-04 Priority changed: MEDIUM → LOW

References

Sources