dbcve.org
Path TraversalWeakness · CWE-22

CVE-2026-58467

HIGH · 7.5 CVSS v3.1 Published 2026-07-02
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 7 weeks old

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
Cockpit CMS through 2.14.0 contains a path traversal and local file inclusion vulnerability that allows unauthenticated attackers to read arbitrary files or execute PHP files by including unvalidated PATH_INFO derived from REQUEST_URI in filesystem path construction without containment checks. Attackers can inject dot-dot sequences into the URL to traverse outside the designated spaces directory, and when the resolved path ends with a .php extension, the application passes it to include(), enabling local file inclusion on deployments using the PHP built-in server or certain non-default Nginx configurations.

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

Cockpit CMS through 2.14.0 has a path traversal and local file inclusion vulnerability where the application uses PATH_INFO derived from REQUEST_URI without validation to construct filesystem paths. Attackers can inject '../' sequences to escape the designated spaces directory and access arbitrary files. When the resolved path ends with .php, the application passes it to include(), enabling code execution.

MitigationUpdate to a patched version when available. Implement strict input validation on PATH_INFO to reject traversal sequences ('../'), whitelist allowed directories, and ensure the application is deployed with a properly configured web server that includes containment safeguards.

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. Confirm Cockpit CMS installation
    Look for the cockpit directory or index.php that includes the Cockpit bootstrap (search for 'Cockpit' or 'cockpit' in PHP files or check for /cockpit/ route handling in your web server.
    Affected if Cockpit CMS is not present in the environment.
  2. Identify installed version
    Check the version file (usually VERSION or cockpit.php in the root directory) or examine composer.json for the cockpit-hq/cockpit package version.
    Affected if The installed version is 2.14.0 or lower (any version through 2.14.0 is affected).
  3. Identify web server type
    Determine if the site runs on the PHP built-in server (check if php -S is used in startup scripts, Procfile, or deployment configuration) or on Nginx.
    Affected if The application uses the PHP built-in server OR a non-default Nginx configuration.
  4. Check for vulnerable URL handling
    Inspect how REQUEST_URI and PATH_INFO are processed in the entry point (index.php) or Nginx configuration; look for direct inclusion of files based on path components without sanitization.
    Affected if The application directly includes files based on PATH_INFO without validating that the resolved path stays within the spaces directory.
  5. Verify .php file inclusion capability
    Test whether a path traversal request ending in .php (e.g., /../../../../etc/passwd.php) is processed by the include() function - check server logs or application behavior.
    Affected if The resolved path ending in .php can be passed to include() without containment checks.

The environment is affected if Cockpit CMS version 2.14.0 or lower is running on the PHP built-in server or a vulnerable Nginx configuration that allows path traversal to inject .. sequences and includes .php files based on unsanitized PATH_INFO.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to a patched version when available. Implement strict input validation on PATH_INFO to reject traversal sequences ('../'), whitelist allowed directories, and ensure the application is deployed with a properly configured web server that includes containment safeguards.

Recommended fix Moderate confidence

Latest stable release after 2.14.0 (verify exact version on GitHub releases)

  1. 1. Check Cockpit CMS official releases on GitHub (github.com/Cockpit-HQ/Cockpit) for versions after 2.14.0
  2. 2. Upgrade to the latest stable release available after 2.14.0 which should contain the path traversal fix
  3. 3. After upgrading, verify the fix by testing that dot-dot sequences (..) in URLs are properly rejected or sanitized
  4. 4. Review server configuration to ensure proper containment within the spaces directory

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-58467 — 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-58467 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