CVE-2026-6074
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIntrado 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCritical path traversal vulnerability in Intrado 911 Emergency Gateway's download_debuglog_file.php endpoint allows unauthenticated attackers to manipulate the 'name' parameter to read arbitrary files from the filesystem, bypassing intended directory restrictions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Intrado EGW is deployedIdentify if Intrado 911 Emergency Gateway software or appliance is installed in your environment. Check network services for EGW management interfaces (typically HTTPS on ports 443, 8443, or vendor-specified ports).Affected if Intrado 911 Emergency Gateway is present in your environment.
-
Determine EGW versionLog into the EGW management interface and locate the version information, typically found in About, System Info, or Settings pages. Alternatively, check the firmware or software build number via CLI if available.Affected if The installed version falls within 5.x, 6.x, or 7.x ranges.
-
Verify vulnerable endpoint existsAttempt to access the download_debuglog_file.php endpoint via HTTP/HTTPS (e.g., GET request to /download_debuglog_file.php). A 200 or 403 response indicates the endpoint is present. A 404 indicates it may not exist or has been removed.Affected if The endpoint returns a valid HTTP response (200, 400, or 403) rather than 404.
-
Check network exposure of management interfaceDetermine if the EGW management interface (web UI and PHP endpoints) is accessible from untrusted networks. Use port scanning or firewall rule review to confirm whether the management port is exposed to the internet or unauthorized VLANs.Affected if The management interface is reachable from untrusted networks or the internet without ACLs.
You are likely affected if Intrado EGW versions 5.x, 6.x, or 7.x are running AND the download_debuglog_file.php endpoint is accessible from your network, particularly if exposed to untrusted access.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataApply vendor-supplied patch for versions 5.x, 6.x, and 7.x immediately; if no patch available, implement strict input validation restricting the name parameter to expected debug log filenames only and consider temporarily disabling the debug log download feature until remediated.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6074 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6074 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data