# CVE-2026-6074: Path traversal: '.../...//' in Intrado 911 Emergency Gateway (EGW)

> Unauthenticated attackers can read arbitrary files via path traversal in the Intrado 911 Emergency Gateway debug log endpoint.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Apr 2026
- **Updated:** 4 Jun 2026
- **Also known as:** CVE-2026-34882, GHSA-7v49-538c-cx3p

## What is CVE-2026-6074?

CVE-2026-6074 is a critical path traversal vulnerability in Intrado 911 Emergency Gateway, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Intrado 911 Emergency Gateway (EGW) 5.x, 6.x, and 7.x contain a path traversal vulnerability in the download_debuglog_file.php endpoint used for Debug Logs downloads. An unauthenticated attacker can manipulate the name parameter to read arbitrary files outside the intended directory.

Weakness: CWE-35 (Path Traversal: '.../...//')

## Which versions are affected by CVE-2026-6074?


## How do I fix CVE-2026-6074?

No fix has been published for CVE-2026-6074 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-6074 being exploited?

There is no known exploitation of CVE-2026-6074 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6074 and fix it if it is affected.

What it is: CVE-2026-6074 is a critical path traversal vulnerability in Intrado 911 Emergency Gateway, published on 23 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6074 in the wild and no public exploit code.

Affected product: Intrado 911 Emergency Gateway. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6074/ (Markdown: https://insights.sbomify.com/CVE-2026-6074/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6074
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6074
- OSV: https://osv.dev/vulnerability/CVE-2026-6074

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6074/
Summaries are generated and may contain mistakes; the official description above is the record.