CVE-2026-65636 (GCVE-0-2026-65636)
Vulnerability from cvelistv5 – Published: 2026-07-31 13:29 – Updated: 2026-08-01 04:18- CWE-93 - Improper Neutralization of CRLF Sequences ('CRLF Injection')
| URL | Tags |
|---|---|
| https://github.com/ufirstgroup/ymlr/security/advi… | vendor-advisoryrelated |
| https://cna.erlef.org/cves/CVE-2026-65636.html | related |
| https://osv.dev/vulnerability/EEF-CVE-2026-65636 | related |
| https://github.com/ufirstgroup/ymlr/commit/7e5306… | patch |
| https://github.com/ufirstgroup/ymlr/commit/42a0bf… | patch |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| ufirstgroup | ymlr |
Affected:
0.0.1 , < 5.1.6
(semver)
cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:* |
||
| ufirstgroup | ymlr |
Affected:
0c11a86de83825e91c27cecaccb03f36416d8fe0 , < 42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc
(git)
cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-65636",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-31T14:28:31.525792Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-31T14:28:44.562Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ymlr",
"packageURL": "pkg:hex/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "5.1.6",
"status": "affected",
"version": "0.0.1",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ufirstgroup/ymlr",
"packageURL": "pkg:github/ufirstgroup/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc",
"status": "affected",
"version": "0c11a86de83825e91c27cecaccb03f36416d8fe0",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA deployment is vulnerable when the host application places attacker-controlled text in the comment position of a document, that is, as the first element of the \u003ctt\u003e{comment, data}\u003c/tt\u003e tuple passed to \u003ctt\u003eYmlr.document!/2\u003c/tt\u003e, \u003ctt\u003eYmlr.document/2\u003c/tt\u003e, \u003ctt\u003eYmlr.documents!/2\u003c/tt\u003e or \u003ctt\u003eYmlr.documents/2\u003c/tt\u003e. Callers that encode data without comments, or that use only static comment strings, are not exploitable.\u003c/p\u003e"
}
],
"value": "A deployment is vulnerable when the host application places attacker-controlled text in the comment position of a document, that is, as the first element of the {comment, data} tuple passed to Ymlr.document!/2, Ymlr.document/2, Ymlr.documents!/2 or Ymlr.documents/2. Callers that encode data without comments, or that use only static comment strings, are not exploitable."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.1.6",
"versionStartIncluding": "0.0.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Michael Ruoss"
},
{
"lang": "en",
"type": "analyst",
"value": "Jonatan M\u00e4nnchen / EEF"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eImproper Neutralization of CRLF Sequences vulnerability in ufirstgroup ymlr (\u003ctt\u003eElixir.Ymlr\u003c/tt\u003e module) allows attackers to inject arbitrary content into generated YAML documents through document comments. \u003ctt\u003eYmlr.document!/2\u003c/tt\u003e interpolates each caller-supplied comment string into the output behind a single \u003ctt\u003e#\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eAn 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 \u003ctt\u003e---\u003c/tt\u003e or \u003ctt\u003e...\u003c/tt\u003e 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 \u003ctt\u003eYmlr.document/2\u003c/tt\u003e, \u003ctt\u003eYmlr.documents!/2\u003c/tt\u003e and \u003ctt\u003eYmlr.documents/2\u003c/tt\u003e, so every document encoding entry point is affected.\u003c/p\u003e\u003cp\u003eThis vulnerability is associated with program files \u003ctt\u003elib/ymlr.ex\u003c/tt\u003e and program routines \u003ctt\u003e\u0027Elixir.Ymlr\u0027:document!/2\u003c/tt\u003e, \u003ctt\u003e\u0027Elixir.Ymlr\u0027:documents!/2\u003c/tt\u003e.\u003c/p\u003e\u003cp\u003eThis issue affects ymlr from 0.0.1 before 5.1.6.\u003c/p\u003e"
}
],
"value": "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.\n\nAn 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.\n\nThis vulnerability is associated with program files lib/ymlr.ex and program routines \u0027Elixir.Ymlr\u0027:document!/2, \u0027Elixir.Ymlr\u0027:documents!/2.\n\nThis issue affects ymlr from 0.0.1 before 5.1.6."
}
],
"impacts": [
{
"capecId": "CAPEC-15",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-15 Command Delimiters"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"baseScore": 2.1,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-93",
"description": "CWE-93 Improper Neutralization of CRLF Sequences (\u0027CRLF Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-01T04:18:38.726Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ufirstgroup/ymlr/security/advisories/GHSA-p8qx-7cp9-v6c9"
},
{
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-65636.html"
},
{
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-65636"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ufirstgroup/ymlr/commit/7e53061fb2809b787fba0373c46b78e253c83adc"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ufirstgroup/ymlr/commit/42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "YAML injection via unescaped newlines in ymlr document comments",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eSplit any untrusted comment string on line breaks and pass the resulting list as the comment element of the \u003ctt\u003e{comment, data}\u003c/tt\u003e tuple. Ymlr prefixes every list element with its own \u003ctt\u003e#\u003c/tt\u003e marker, so no line can leave the comment context. Alternatively, reject comment strings that contain carriage return or line feed characters, or keep untrusted text out of comments entirely and place it in the encoded data instead, where the encoder quotes it.\u003c/p\u003e"
}
],
"value": "Split any untrusted comment string on line breaks and pass the resulting list as the comment element of the {comment, data} tuple. Ymlr prefixes every list element with its own # marker, so no line can leave the comment context. Alternatively, reject comment strings that contain carriage return or line feed characters, or keep untrusted text out of comments entirely and place it in the encoded data instead, where the encoder quotes it."
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-65636",
"datePublished": "2026-07-31T13:29:31.198Z",
"dateReserved": "2026-07-22T13:58:26.233Z",
"dateUpdated": "2026-08-01T04:18:38.726Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-65636",
"date": "2026-11-16",
"epss": "0.00197",
"percentile": "0.09437"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ymlr",
"packageURL": "pkg:hex/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "5.1.6",
"status": "affected",
"version": "0.0.1",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ufirstgroup/ymlr",
"packageURL": "pkg:github/ufirstgroup/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc",
"status": "affected",
"version": "0c11a86de83825e91c27cecaccb03f36416d8fe0",
"versionType": "git"
}
]
}
],
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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.\n\nAn 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.\n\nThis vulnerability is associated with program files lib/ymlr.ex and program routines \u0027Elixir.Ymlr\u0027:document!/2, \u0027Elixir.Ymlr\u0027:documents!/2.\n\nThis issue affects ymlr from 0.0.1 before 5.1.6."
},
{
"lang": "es",
"value": "La vulnerabilidad de neutralizaci\u00f3n incorrecta de secuencias CRLF en ufirstgroup ymlr (m\u00f3dulo Elixir.Ymlr) permite a los atacantes inyectar contenido arbitrario en documentos YAML generados a trav\u00e9s de comentarios de documentos. Ymlr.document!/2 interpola cada cadena de comentario proporcionada por el llamador en la salida detr\u00e1s de un \u00fanico prefijo # sin validarla o escapar los saltos de l\u00ednea. Debido a que un comentario YAML termina con un salto de l\u00ednea, el primer retorno de carro o salto de l\u00ednea en la cadena de comentario finaliza el contexto del comentario y todo lo que le sigue se emite en la columna 0 del cuerpo del documento.\n\nUn atacante que controla el texto que la aplicaci\u00f3n anfitriona pasa como comentario puede falsificar claves de mapeo de nivel superior, anular valores que la propia aplicaci\u00f3n estableci\u00f3 y emitir marcadores --- o ... que dividen la salida en documentos adicionales. Los consumidores posteriores del YAML generado, como cargadores de configuraci\u00f3n, manifiestos de despliegue, pipelines de CI e importadores de datos, analizan el contenido inyectado como datos leg\u00edtimos. La misma cl\u00e1usula respalda Ymlr.document/2, Ymlr.documents!/2 y Ymlr.documents/2, por lo que cada punto de entrada de codificaci\u00f3n de documentos se ve afectado.\n\nEsta vulnerabilidad est\u00e1 asociada con los archivos de programa lib/ymlr.ex y las rutinas de programa Elixir.Ymlr:document!/2, Elixir.Ymlr:documents!/2.\n\nEste problema afecta a ymlr desde 0.0.1 antes de 5.1.6."
}
],
"id": "CVE-2026-65636",
"lastModified": "2026-10-23T23:10:00.157",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 2.1,
"baseSeverity": "LOW",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-65636",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-31T14:28:31.525792Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-07-31T14:16:51.240",
"references": [
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://cna.erlef.org/cves/CVE-2026-65636.html"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ufirstgroup/ymlr/commit/42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ufirstgroup/ymlr/commit/7e53061fb2809b787fba0373c46b78e253c83adc"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ufirstgroup/ymlr/security/advisories/GHSA-p8qx-7cp9-v6c9"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-65636"
}
],
"sourceIdentifier": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"vulnStatus": "Awaiting Analysis",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-93"
}
],
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-65636",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-07-31T14:28:31.525792Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-07-31T14:28:39.454Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ymlr",
"packageURL": "pkg:hex/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "5.1.6",
"status": "affected",
"version": "0.0.1",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"Elixir.Ymlr"
],
"packageName": "ufirstgroup/ymlr",
"packageURL": "pkg:github/ufirstgroup/ymlr",
"product": "ymlr",
"programFiles": [
"lib/ymlr.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.Ymlr\u0027:document!/2"
},
{
"name": "\u0027Elixir.Ymlr\u0027:documents!/2"
}
],
"repo": "https://github.com/ufirstgroup/ymlr",
"vendor": "ufirstgroup",
"versions": [
{
"lessThan": "42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc",
"status": "affected",
"version": "0c11a86de83825e91c27cecaccb03f36416d8fe0",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA deployment is vulnerable when the host application places attacker-controlled text in the comment position of a document, that is, as the first element of the \u003ctt\u003e{comment, data}\u003c/tt\u003e tuple passed to \u003ctt\u003eYmlr.document!/2\u003c/tt\u003e, \u003ctt\u003eYmlr.document/2\u003c/tt\u003e, \u003ctt\u003eYmlr.documents!/2\u003c/tt\u003e or \u003ctt\u003eYmlr.documents/2\u003c/tt\u003e. Callers that encode data without comments, or that use only static comment strings, are not exploitable.\u003c/p\u003e"
}
],
"value": "A deployment is vulnerable when the host application places attacker-controlled text in the comment position of a document, that is, as the first element of the {comment, data} tuple passed to Ymlr.document!/2, Ymlr.document/2, Ymlr.documents!/2 or Ymlr.documents/2. Callers that encode data without comments, or that use only static comment strings, are not exploitable."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ufirstgroup:ymlr:*:*:*:*:*:*:*:*",
"versionEndExcluding": "5.1.6",
"versionStartIncluding": "0.0.1",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Peter Ullrich"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Michael Ruoss"
},
{
"lang": "en",
"type": "analyst",
"value": "Jonatan M\u00e4nnchen / EEF"
}
],
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eImproper Neutralization of CRLF Sequences vulnerability in ufirstgroup ymlr (\u003ctt\u003eElixir.Ymlr\u003c/tt\u003e module) allows attackers to inject arbitrary content into generated YAML documents through document comments. \u003ctt\u003eYmlr.document!/2\u003c/tt\u003e interpolates each caller-supplied comment string into the output behind a single \u003ctt\u003e#\u003c/tt\u003e 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.\u003c/p\u003e\u003cp\u003eAn 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 \u003ctt\u003e---\u003c/tt\u003e or \u003ctt\u003e...\u003c/tt\u003e 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 \u003ctt\u003eYmlr.document/2\u003c/tt\u003e, \u003ctt\u003eYmlr.documents!/2\u003c/tt\u003e and \u003ctt\u003eYmlr.documents/2\u003c/tt\u003e, so every document encoding entry point is affected.\u003c/p\u003e\u003cp\u003eThis vulnerability is associated with program files \u003ctt\u003elib/ymlr.ex\u003c/tt\u003e and program routines \u003ctt\u003e\u0027Elixir.Ymlr\u0027:document!/2\u003c/tt\u003e, \u003ctt\u003e\u0027Elixir.Ymlr\u0027:documents!/2\u003c/tt\u003e.\u003c/p\u003e\u003cp\u003eThis issue affects ymlr from 0.0.1 before 5.1.6.\u003c/p\u003e"
}
],
"value": "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.\n\nAn 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.\n\nThis vulnerability is associated with program files lib/ymlr.ex and program routines \u0027Elixir.Ymlr\u0027:document!/2, \u0027Elixir.Ymlr\u0027:documents!/2.\n\nThis issue affects ymlr from 0.0.1 before 5.1.6."
}
],
"impacts": [
{
"capecId": "CAPEC-15",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-15 Command Delimiters"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "LOCAL",
"baseScore": 2.1,
"baseSeverity": "LOW",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "LOW",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:L/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "LOW"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-93",
"description": "CWE-93 Improper Neutralization of CRLF Sequences (\u0027CRLF Injection\u0027)",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-08-01T04:18:38.726Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ufirstgroup/ymlr/security/advisories/GHSA-p8qx-7cp9-v6c9"
},
{
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-65636.html"
},
{
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-65636"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ufirstgroup/ymlr/commit/7e53061fb2809b787fba0373c46b78e253c83adc"
},
{
"tags": [
"patch"
],
"url": "https://github.com/ufirstgroup/ymlr/commit/42a0bf8b2af44b0e7c42d0b7044c8588ca5866dc"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "YAML injection via unescaped newlines in ymlr document comments",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eSplit any untrusted comment string on line breaks and pass the resulting list as the comment element of the \u003ctt\u003e{comment, data}\u003c/tt\u003e tuple. Ymlr prefixes every list element with its own \u003ctt\u003e#\u003c/tt\u003e marker, so no line can leave the comment context. Alternatively, reject comment strings that contain carriage return or line feed characters, or keep untrusted text out of comments entirely and place it in the encoded data instead, where the encoder quotes it.\u003c/p\u003e"
}
],
"value": "Split any untrusted comment string on line breaks and pass the resulting list as the comment element of the {comment, data} tuple. Ymlr prefixes every list element with its own # marker, so no line can leave the comment context. Alternatively, reject comment strings that contain carriage return or line feed characters, or keep untrusted text out of comments entirely and place it in the encoded data instead, where the encoder quotes it."
}
],
"x_generator": {
"engine": "cvelib 1.8.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-65636",
"datePublished": "2026-07-31T13:29:31.198Z",
"dateReserved": "2026-07-22T13:58:26.233Z",
"dateUpdated": "2026-08-01T04:18:38.726Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Workarounds
Configurations
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.