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.2% (8th percentile of EPSS-scored CVEs). 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.2%CVSS: 2.1Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

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.1LOWmedium confidence
EG Risk
25
EG Risk 25/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
8th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 31, 2026

Last Modified

August 4, 2026

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
ymlr0.0.1 ... 5.1.5 (17 versions)
  • 0.0.1 up to 5.1.6: fixed in 5.1.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 28× 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-10-10 20:00 UTCEPSS rescore
  2. 2026-10-09 20:07 UTCEPSS rescore
  3. 2026-10-08 17:13 UTCEPSS rescore
  4. 2026-10-07 23:48 UTCEPSS rescore
  5. 2026-10-07 01:25 UTCEG score recompute
  6. 2026-10-06 15:18 UTCEPSS rescore
  7. 2026-10-05 17:43 UTCEPSS rescore
  8. 2026-10-04 23:22 UTCEPSS rescore
  9. 2026-10-04 06:32 UTCEG score recompute
  10. 2026-10-03 14:26 UTCEPSS rescore
  11. 2026-10-02 17:56 UTCEPSS rescore
  12. 2026-10-01 19:50 UTCEPSS rescore
  13. 2026-10-01 02:48 UTCEG score recompute
  14. 2026-09-30 15:03 UTCEPSS rescore
  15. 2026-09-28 13:51 UTCEPSS rescore
  16. 2026-09-28 02:52 UTCEG score recompute
  17. 2026-09-26 15:59 UTCEPSS rescore
  18. 2026-09-25 04:52 UTCEG score recompute
  19. 2026-09-23 17:54 UTCEPSS rescore
  20. 2026-09-22 07:46 UTCEG score recompute
  21. 2026-09-20 20:16 UTCEPSS rescore
  22. 2026-09-18 23:59 UTCEG score recompute
  23. 2026-09-18 19:28 UTCEPSS rescore
  24. 2026-09-16 14:08 UTCEPSS rescore
  25. 2026-09-16 05:29 UTCEG score recompute
Show 57 more
  1. 2026-09-16 05:15 UTCEPSS rescore
  2. 2026-09-13 08:57 UTCEG score recompute
  3. 2026-09-11 09:37 UTCEPSS rescore
  4. 2026-09-10 14:29 UTCEG score recompute
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 19:34 UTCEG score recompute
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 13:47 UTCEPSS rescore
  9. 2026-09-05 15:31 UTCEPSS rescore
  10. 2026-09-04 17:03 UTCEG score recompute
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 22:33 UTCEG score recompute
  14. 2026-09-01 13:54 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-29 22:22 UTCEG score recompute
  19. 2026-08-28 21:42 UTCEPSS rescore
  20. 2026-08-26 19:16 UTCEG score recompute
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-24 00:10 UTCEG score recompute
  24. 2026-08-23 00:19 UTCEPSS rescore
  25. 2026-08-21 23:49 UTCEPSS rescore
  26. 2026-08-21 05:43 UTCEG score recompute
  27. 2026-08-20 22:56 UTCEPSS rescore
  28. 2026-08-19 17:04 UTCEPSS rescore
  29. 2026-08-18 13:48 UTCEPSS rescore
  30. 2026-08-18 11:16 UTCEG score recompute
  31. 2026-08-17 13:47 UTCEPSS rescore
  32. 2026-08-16 14:56 UTCEPSS rescore
  33. 2026-08-15 16:44 UTCEG score recompute
  34. 2026-08-15 01:30 UTCEPSS rescore
  35. 2026-08-13 22:00 UTCEPSS rescore
  36. 2026-08-12 22:16 UTCEG score recompute
  37. 2026-08-12 13:51 UTCEPSS rescore
  38. 2026-08-11 00:00 UTCEPSS rescore
  39. 2026-08-10 03:49 UTCEG score recompute
  40. 2026-08-09 13:47 UTCEPSS rescore
  41. 2026-08-08 16:37 UTCEPSS rescore
  42. 2026-08-07 09:22 UTCEG score recompute
  43. 2026-08-06 13:47 UTCEPSS rescore
  44. 2026-08-05 19:17 UTCEPSS rescore
  45. 2026-08-05 19:17 UTCEPSS rescore
  46. 2026-08-04 15:10 UTCEPSS rescore
  47. 2026-08-04 14:55 UTCEG score recompute
  48. 2026-08-04 10:39 UTCEPSS rescore
  49. 2026-08-03 23:16 UTCEG score recompute
  50. 2026-08-03 10:36 UTCEPSS rescore
  51. 2026-08-02 02:27 UTCEPSS rescore
  52. 2026-08-01 04:48 UTCEG score recompute
  53. 2026-07-31 15:27 UTCEG score recompute
  54. 2026-07-31 14:51 UTCEG score recompute
  55. 2026-07-31 14:24 UTCEG score recompute
  56. 2026-07-31 13:59 UTCEG score recompute
  57. 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 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.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-65636?
CVE-2026-65636 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-65636?
A fix for CVE-2026-65636 is available: update to the fixed version the vendor names in its advisory.

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.