SEPTEMBER 15, 2026
Live Feed
Back to database
Case File

CVE-2026-65636

LOW · CVSS 2.1 EPSS 0.14% Public Exploit

Source: NVD + CISA KEV + EPSS · Published 2026-07-31 · Last synced 2026-08-30

CyberRota Analysis

AI-Generated

The Elixir Ymlr module is vulnerable to improper neutralization of CRLF sequences, allowing attackers to inject arbitrary content into generated YAML documents via unvalidated comments. This can lead to the manipulation of top-level mapping keys and values, potentially compromising configuration loaders, CI pipelines, and other systems that parse the affected YAML output. Organizations using Ymlr versions prior to 5.1.6 should prioritize patching this vulnerability to mitigate risks associated with unauthorized data manipulation.

Public Exploit Signal

A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.

Note: these links are listed for security research and verification purposes only.

CVE
CVE-2026-65636
Severity
LOW
CVSS
2.1
EPSS
0.14%

Original NVD 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.