CVE-2026-65636

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
2.1EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.1Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
2.1
EG Score
2.1(medium)
EG Risk
25(Track)
EG Risk 25/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity21% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

July 31, 2026

Last Modified

August 4, 2026

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ymlr0.0.1 ... 5.1.5 (17 versions)5.1.6

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 38× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-26 19:16 UTCEG score recompute
  2. 2026-08-26 14:47 UTCEPSS rescore
  3. 2026-08-25 13:49 UTCEPSS rescore
  4. 2026-08-24 00:10 UTCEG score recompute
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-21 05:43 UTCEG score recompute
  8. 2026-08-20 22:56 UTCEPSS rescore
  9. 2026-08-19 17:04 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-18 11:16 UTCEG score recompute
  12. 2026-08-17 13:47 UTCEPSS rescore
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-15 16:44 UTCEG score recompute
  15. 2026-08-15 01:30 UTCEPSS rescore
  16. 2026-08-13 22:00 UTCEPSS rescore
  17. 2026-08-12 22:16 UTCEG score recompute
  18. 2026-08-12 13:51 UTCEPSS rescore
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-10 03:49 UTCEG score recompute
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-07 09:22 UTCEG score recompute
  24. 2026-08-06 13:47 UTCEPSS rescore
  25. 2026-08-05 19:17 UTCEPSS rescore
Show 13 more
  1. 2026-08-05 19:17 UTCEPSS rescore
  2. 2026-08-04 15:10 UTCEPSS rescore
  3. 2026-08-04 14:55 UTCEG score recompute
  4. 2026-08-04 10:39 UTCEPSS rescore
  5. 2026-08-03 23:16 UTCEG score recompute
  6. 2026-08-03 10:36 UTCEPSS rescore
  7. 2026-08-02 02:27 UTCEPSS rescore
  8. 2026-08-01 04:48 UTCEG score recompute
  9. 2026-07-31 15:27 UTCEG score recompute
  10. 2026-07-31 14:51 UTCEG score recompute
  11. 2026-07-31 14:24 UTCEG score recompute
  12. 2026-07-31 13:59 UTCEG score recompute
  13. 2026-07-31 13:58 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-65636?
CVE-2026-65636 is a low vulnerability published on July 31, 2026. 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 #…
When was CVE-2026-65636 disclosed?
CVE-2026-65636 was first published in the National Vulnerability Database on July 31, 2026, with the most recent update on August 4, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-65636 actively exploited?
CVE-2026-65636 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.3% of all scored CVEs.
What is the CVSS score of CVE-2026-65636?
CVE-2026-65636 has a CVSS v3 base score of 2.1 (NVD).
How do I remediate CVE-2026-65636?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-65636, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-65636

Explore →

Is Your Infrastructure Affected by CVE-2026-65636?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.