CVE-2026-42598
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 · uneditedPode is a Cross-Platform PowerShell web framework for creating REST APIs, Web Sites, and TCP/SMTP servers. From 2.4.0, to before 2.13.0, when requesting content from a Static Route, it was possible to request paths such as http://localhost:8080/c:/Windows/System32/drivers/etc/hosts and have the contents returned. This vulnerability is fixed in 2.13.0.
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 confidenceA path traversal vulnerability in Pode's Static Route functionality (versions 2.4.0 to before 2.13.0) allows attackers to access arbitrary files on the host filesystem by including absolute Windows-style paths (e.g., c:/Windows/System32/drivers/etc/hosts) in URL requests, bypassing the intended static file 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
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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.
-
Identify installed Pode versionRun 'Get-Module -ListAvailable Pode' or check the Pode.psd1 version metadata, or inspect the module folder name under $env:PSModulePathAffected if The version is 2.4.0 or higher but lower than 2.13.0
-
Confirm Static Routes are in useSearch configuration files (.ps1/.psd1) for 'New-PodeStaticRoute' cmdlet calls or 'Static' route definitions in your Pode application codeAffected if Static Routes are defined and configured to serve files from disk
-
Check static route source directoryInspect the -RootPath or -Path parameter in your New-PodeStaticRoute calls to identify which directories are configured for static file servingAffected if Static routes serve files from any directory on the filesystem (not contained in memory-only paths)
-
Test for path traversal with Windows absolute pathSend an HTTP request to a static endpoint using a Windows-style absolute path such as '/c:/Windows/System32/drivers/etc/hosts' or the equivalent path separator format your server acceptsAffected if The request returns content from outside the intended static root directory, confirming the vulnerability is present
You are affected if running Pode 2.4.0 through 2.12.x AND you have Static Routes configured to serve files from disk, as an attacker can escape the intended directory using absolute Windows paths in requests.
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.
dbcve · scopedUpgrade to Pode version 2.13.0 or later which contains the fix for proper path validation in Static Routes.
2.13.0
- Check the current installed version of Pode in the project (e.g., check the module version with `Get-Module -ListAvailable Pode` or inspect the project's dependencies)
- Identify if the version is between 2.4.0 and 2.12.x (inclusive) - these versions are affected by the path traversal vulnerability
- Upgrade the Pode module/package to version 2.13.0 or later (the latest stable release recommended)
- After upgrading, verify that Static Routes properly restrict path access and no longer permit traversal to absolute Windows paths or other arbitrary file system locations
- Deploy the updated application to production environments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42598 — 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-42598 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