CVE-2026-120455
Received Received - Intake

RapidYAML Out-of-Bounds Write via Excess Anchors

Vulnerability report for CVE-2026-120455, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-02

Last updated on: 2026-11-02

Assigner: VulnCheck

Description

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-02
Last Modified
2026-11-02
Generated
2026-11-02
AI Q&A
2026-11-02
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
biojppm rapidyaml 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-787 The product writes data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an out-of-bounds write vulnerability in the rapidyaml library through version 0.16.0. It occurs in the ParseEngine::_add_annotation() function where a fixed two-element array is used to store annotations. When YAML input contains three or more consecutive anchors or tags, the array overflows, corrupting stack memory and potentially crashing the process.

Detection Guidance

To detect this vulnerability, inspect YAML inputs processed by rapidyaml v0.16.0 or earlier for consecutive anchors or tags. Test with inputs like flow-style YAML `[&a &b &c x]` or block-style YAML with three lines of tags `!a`, `!b`, `!c`. If parsing crashes or produces unexpected behavior, the system may be vulnerable.

Impact Analysis

The vulnerability can cause memory corruption leading to application crashes. While it does not directly enable arbitrary code execution or information disclosure, the stack corruption could potentially lead to denial of service or unstable behavior in applications using rapidyaml for YAML parsing.

Compliance Impact

This vulnerability does not directly impact compliance with GDPR or HIPAA as it is a memory corruption issue in a YAML parser library. It may indirectly affect compliance if the library is used in systems handling sensitive data, potentially leading to crashes or undefined behavior that could disrupt data processing or security controls.

Mitigation Strategies

Upgrade rapidyaml to a patched version where the capacity check in `_add_annotation` is always enforced. If upgrading is not possible, avoid processing untrusted YAML inputs with excessive anchors or tags until a fix is applied.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120455. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...