CVE-2026-65636

YAML injection via unescaped newlines in ymlr document comments

LOW
2.1
CVSS Score
Published: July 31, 2026 at 01:29 PM UTC
Updated: October 23, 2026 at 11:10 PM UTC
1 product affected across 1 vendorYmlr

Using ymlr by ufirstgroup?

Get instant alerts when new vulnerabilities affect ymlr - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
LOW2.1
Exploit prediction
EPSS 0.2%
SSVC
PoC

Description

Improper Neutralization of CRLF Sequences vulnerability in ufirstgroup ymlr (Elixir.Ymlr module) allows attackers to inject arbitrary content into generated YAML documents through document comments. Ymlr.document!/2 interpolates each caller-supplied comment string into the output behind a single # prefix without validating it or escaping line breaks. Because a YAML comment is terminated by a line break, the first carriage return or line feed in the comment string ends the comment context and everything after it is emitted at column 0 of the document body. An attacker who controls text that the host application passes as a comment can forge top-level mapping keys, override values the application itself set, and emit --- or ... markers that split the output into additional documents. Downstream consumers of the generated YAML, such as configuration loaders, deployment manifests, CI pipelines and data importers, parse the injected content as legitimate data. The same clause backs Ymlr.document/2, Ymlr.documents!/2 and Ymlr.documents/2, so every document encoding entry point is affected. This vulnerability is associated with program files lib/ymlr.ex and program routines 'Elixir.Ymlr':document!/2, 'Elixir.Ymlr':documents!/2. This issue affects ymlr from 0.0.1 before 5.1.6.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions0.0.10c11a86de83825e91c27cecaccb03f36416d8fe0
Vendor states this is fixed in 42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc (fixed)
Affected range stops below 5.1.6, so it looks safe — our inference, not a vendor statement

SSVC — Action Prioritization

SSVCPoCNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

2.1LOWEEF
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-93

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card