UBUNTU-CVE-2026-55847 (CVE-2026-55847)
Vulnerability from osv_ubuntu – Published: 2026-09-14 18:17 – Updated: 2026-09-16 11:36 – Source websiteAllure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. Prior to 2.39.0, the ansi.js helper at allure-generator/src/main/javascript/helpers/ansi.js passes attacker-influenced statusMessage and statusTrace values through AnsiToHtml without HTML escaping and wraps the result in Handlebars SafeString, disabling template auto-escaping in allure-generator/src/main/javascript/blocks/status-details/status-details.hbs. JunitXmlPlugin.java can populate these fields directly from crafted JUnit XML failure messages and traces, and equivalent input flows exist in the TRX, xUnit XML, xctest, and Allure1 and Allure2 plugins. When a user views the affected status details, unescaped markup executes arbitrary JavaScript in the report origin, which can expose report data and compromise sessions associated with that origin. This is an incomplete-fix case because PR 3271 escaped link helpers but did not address the ANSI helper. This issue is fixed in version 2.39.0.
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "allure",
"binary_version": "0.5.0.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:18.04:LTS",
"name": "allure",
"purl": "pkg:deb/ubuntu/allure@0.5.0.0-1?arch=source\u0026distro=bionic"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.5.0.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "allure",
"binary_version": "0.8.3.0-3build3"
}
]
},
"package": {
"ecosystem": "Ubuntu:20.04:LTS",
"name": "allure",
"purl": "pkg:deb/ubuntu/allure@0.8.3.0-3build3?arch=source\u0026distro=focal"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.8.3.0-3build1",
"0.8.3.0-3build2",
"0.8.3.0-3build3"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "allure",
"binary_version": "0.9.5.0-2build1"
}
]
},
"package": {
"ecosystem": "Ubuntu:22.04:LTS",
"name": "allure",
"purl": "pkg:deb/ubuntu/allure@0.9.5.0-2build1?arch=source\u0026distro=jammy"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.9.5.0-2build1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "allure",
"binary_version": "0.11.0.0-1"
}
]
},
"package": {
"ecosystem": "Ubuntu:24.04:LTS",
"name": "allure",
"purl": "pkg:deb/ubuntu/allure@0.11.0.0-1?arch=source\u0026distro=noble"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0.0-1"
]
},
{
"ecosystem_specific": {
"binaries": [
{
"binary_name": "allure",
"binary_version": "0.11.0.0-2"
}
]
},
"package": {
"ecosystem": "Ubuntu:26.04:LTS",
"name": "allure",
"purl": "pkg:deb/ubuntu/allure@0.11.0.0-2?arch=source\u0026distro=resolute"
},
"ranges": [
{
"events": [
{
"introduced": "0"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.11.0.0-1",
"0.11.0.0-1build1",
"0.11.0.0-2"
]
}
],
"aliases": [],
"details": "Allure 2 is the version 2.x branch of Allure Report, a multi-language test reporting tool. Prior to 2.39.0, the ansi.js helper at allure-generator/src/main/javascript/helpers/ansi.js passes attacker-influenced statusMessage and statusTrace values through AnsiToHtml without HTML escaping and wraps the result in Handlebars SafeString, disabling template auto-escaping in allure-generator/src/main/javascript/blocks/status-details/status-details.hbs. JunitXmlPlugin.java can populate these fields directly from crafted JUnit XML failure messages and traces, and equivalent input flows exist in the TRX, xUnit XML, xctest, and Allure1 and Allure2 plugins. When a user views the affected status details, unescaped markup executes arbitrary JavaScript in the report origin, which can expose report data and compromise sessions associated with that origin. This is an incomplete-fix case because PR 3271 escaped link helpers but did not address the ANSI helper. This issue is fixed in version 2.39.0.",
"id": "UBUNTU-CVE-2026-55847",
"modified": "2026-09-16T11:36:39Z",
"published": "2026-09-14T18:17:00Z",
"references": [
{
"type": "REPORT",
"url": "https://ubuntu.com/security/CVE-2026-55847"
},
{
"type": "REPORT",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55847"
}
],
"related": [],
"schema_version": "1.7.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N",
"type": "CVSS_V3"
},
{
"score": "medium",
"type": "Ubuntu"
}
],
"upstream": [
"CVE-2026-55847"
]
}
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.
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.