Security readout for executives and security teams
Plain-English summary
CVE-2026-24469 affects frustratedProton http-server versions 1.0 and below. A remote unauthenticated user can request paths that escape the intended web directory and read files from the server filesystem. The main business risk is exposure of secrets, configuration files, source code, or other sensitive local data. No patch is identified in the provided sources.
Executive priority
Treat as high priority for any exposed deployment because unauthenticated remote file disclosure can reveal credentials or sensitive business data. Prioritize asset discovery, exposure reduction, and vendor advisory monitoring. If the product is not used, no action beyond documentation is needed.
Technical view
The flaw is CWE-22 path traversal in RequestHandler::handleRequest. User-controlled URL path data is used to derive a filename and concatenated with files_directory without adequate sanitization. Crafted GET requests containing traversal sequences can read files outside the intended root. CVSS is 7.5, network exploitable, low complexity, no privileges, no user interaction, confidentiality impact high.
Likely exposure
Exposure is likely where frustratedProton http-server version 1.0 or earlier is deployed and reachable over a network. Internet-facing deployments have higher risk. The sources do not provide CPEs, package ecosystem details, or evidence of widespread deployment.
Exploitation context
The issue is remotely exploitable without authentication and targets confidentiality only. The provided sources do not state active exploitation, and the CVE is not marked as KEV. Practical impact depends on what files the server process can read and whether sensitive files exist on the host.
Researcher notes
Evidence is limited to the CVE record and GitHub advisory. No patch, workaround, exploit-in-the-wild evidence, or affected commit range beyond versions <=1.0 is provided. Validate findings in controlled environments without disclosing sensitive host files.
Mitigation direction
- Check vendor advisory for updated fix guidance before deploying changes.
- Remove or restrict network access to affected deployments where possible.
- Avoid internet exposure until a vendor fix or safe workaround is confirmed.
- Run the service with least filesystem read permissions.
- Ensure served files are confined to non-sensitive directories.
Validation and detection
- Inventory systems for frustratedProton http-server version 1.0 or below.
- Review application code for unsafe path concatenation in RequestHandler::handleRequest.
- Confirm the configured files_directory does not contain sensitive material.
- Check server logs for suspicious traversal-like path requests.
- Monitor the GitHub advisory for patch or mitigation updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-24469 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/frustratedProton/http-server/security/advisories/GHSA-qp54-6gfq-3gffCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.