dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-22905

HIGH · 7.5 CVSS v3.1 Published 2026-02-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An unauthenticated remote attacker can bypass authentication by exploiting insufficient URI validation and using path traversal sequences (e.g., /js/../cgi-bin/post.cgi), gaining unauthorized access to protected CGI endpoints and configuration downloads.

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 confidence

Unauthenticated remote attackers can bypass authentication by sending specially crafted HTTP requests containing path traversal sequences (e.g., /js/../cgi-bin/post.cgi). The insufficient URI validation allows attackers to navigate past authentication checks and access protected CGI endpoints and download sensitive configuration files.

MitigationImplement proper URI normalization and validation before authentication checks, including canonicalization of path components and rejection of traversal sequences like '../'. Additionally, enforce strict allow-lists for permitted CGI endpoints and configuration file access.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify CGI endpoints in the application
    Review web server configuration files and document root for CGI scripts (typically in /cgi-bin/ or .cgi files). Use directory listing or grep for 'cgi-bin', '.cgi' patterns in configuration files.
    Affected if The product exposes CGI scripts that should require authentication but rely on URI-based access controls
  2. Check if authentication is performed before URI validation
    Review the authentication/authorization code flow to determine if URI normalization (resolving '../' sequences) occurs before or after the authentication check. Look for path handling functions in the authentication module.
    Affected if Authentication logic processes the raw requested URI without normalizing path traversal sequences first
  3. Test for path traversal authentication bypass
    Send HTTP requests with path traversal sequences to access protected CGI endpoints, for example: GET /js/../cgi-bin/post.cgi or GET /../etc/passwd (or similar configuration file paths). Compare responses to authenticated requests.
    Affected if Requests with '../' sequences successfully reach protected CGI endpoints or return sensitive files that should require authentication
  4. Inspect URI validation logic
    Search codebase or configuration for URI validation functions. Check if path canonicalization or traversal sequence rejection is implemented before authentication. Look for functions that normalize paths or reject '../' patterns.
    Affected if No URI normalization or path traversal rejection is found in the authentication pipeline, or raw URI is passed directly to authentication checks
  5. Verify allow-listing for CGI endpoints and config files
    Check if the application implements an explicit allow-list of permitted CGI endpoints and blocks access to all other paths by default.
    Affected if No explicit allow-list is enforced, and unauthenticated access to arbitrary paths is possible via traversal sequences

A user is affected if their product exposes CGI endpoints and performs authentication after (or without) normalizing path traversal sequences in the requested URI.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper URI normalization and validation before authentication checks, including canonicalization of path components and rejection of traversal sequences like '../'. Additionally, enforce strict allow-lists for permitted CGI endpoints and configuration file access.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-22905 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-22905 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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