Unrated

Path Traversal Arbitrary File Read in Allure Report built-in HTTP server

IdentifiersCVE-2026-55846CWE-22

CVE-2026-55846 is a path traversal vulnerability in the built-in HTTP server used by Allure Report's allure serve and allure open functionality. Based on the provided advisory, the server fails to properly constrain requested paths to the intended report directory, allowing crafted request paths to traverse outside the served content root and access arbitrary files readable by the Allure process. The issue affects io.qameta.allure:allure-commandline prior to 2.39.0.

For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

Start free trial

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A remote attacker who can reach the Allure HTTP server can read arbitrary files accessible to the Allure process. This may expose sensitive material including system credentials, SSH keys, cloud credentials, environment variables, configuration files, source code, and CI/CD secrets. In environments where Allure is run in shared infrastructure, containers, or CI/CD systems, the disclosure could enable follow-on compromise of adjacent systems, accounts, or pipelines.

Mitigation

If you can’t patch tonight, do this now.

Until patched, avoid exposing the built-in Allure HTTP server to untrusted networks or users. Keep the service bound to localhost where possible and avoid using --host 0.0.0.0 or any externally reachable interface. Apply network-layer restrictions to the listening port, particularly in CI/CD, containerized, shared-user, or multi-tenant environments. Do not expose the server to untrusted clients before upgrading.

Remediation

Patch, then assume compromise.

Upgrade io.qameta.allure:allure-commandline to version 2.39.0 or later. According to the provided advisory, the fix should normalize the resolved request path and verify that it remains within the report directory before serving content, rejecting traversal attempts with an HTTP 403 response.

PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType

QametaAllure-Commandlineapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

No public activity tracked yet. Mallory keeps watching.

0 SOURCESView more in app

No public activity observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.

Start free trial

Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity