Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-58467 – Path Traversal / Local File Inclusion – Cockpit CMS before release 364

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-58467 is a path traversal and local file inclusion (LFI) vulnerability in Cockpit CMS, a PHP-based headless content management system. The flaw allows unauthenticated remote attackers to read arbitrary files from the server filesystem, and under specific server configurations, to execute arbitrary PHP files via PHP’s native include() function. The vulnerability carries a CVSS 4.0 score of 8.2 (High) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: Cockpit CMS includes unvalidated PATH_INFO derived from REQUEST_URI directly in filesystem path construction, with no containment checks to ensure the resolved path stays within the application’s designated spaces directory.
  • Attack mechanism: An unauthenticated attacker injects dot-dot sequences (../) into the URL path. This allows traversal outside the CMS’s designated spaces directory to arbitrary locations on the server filesystem.
  • LFI escalation: When the traversed path resolves to a filename with a .php extension, the application passes it directly to PHP’s include() function. On deployments running the PHP built-in server, or under certain non-default Nginx configurations, this enables local file inclusion and potential code execution.
  • Attack vector: Network — no authentication, no user interaction required. Exploitation is achievable with a crafted HTTP request.
  • Impact: Unauthenticated arbitrary file read, exposing sensitive files such as credentials, configuration secrets, and private keys. Under applicable server configurations, the LFI path creates a vector for PHP code execution.

Affected software

  • Cockpit CMS — all releases prior to release 364

Severity

  • CVSS 4.0 base score: 8.2 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade Cockpit CMS to release 364 or later, which contains the vendor-provided fix.
  • If immediate patching is not feasible:
    • Restrict external network access to the Cockpit CMS admin interface using a firewall or WAF rule.
    • Ensure the PHP built-in server is not used in any production deployment of Cockpit CMS.
    • Review Nginx configurations to enforce proper path normalization and containment, preventing traversal sequences from reaching the application.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge