CVE-2026-13533
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 · uneditedA security vulnerability has been detected in agentejo Cockpit CMS up to 0.12.2. Affected by this issue is the function Spyc::YAMLLoad of the file /config/config.yaml of the component htaccess Handler. Such manipulation leads to files or directories accessible. It is possible to launch the attack remotely. The exploit has been disclosed publicly and may be used. Configuration settings should be changed. The vendor was contacted early about this disclosure but did not respond in any way.
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 · moderate confidenceCockpit CMS versions up to 0.12.2 contain a vulnerability in the Spyc::YAMLLoad function used by the htaccess Handler when processing /config/config.yaml. The improper handling of YAML parsing allows attackers to access files or directories on the system, likely through path traversal sequences embedded in malicious YAML input.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Cockpit CMS installationLook for Cockpit CMS in your web application's directory structure, typically in the root folder where CMS packages are deployed. Check for known Cockpit files such as index.php, composer.json, or the /cockpit directory.Affected if Cockpit CMS is present in the environment
-
Determine installed Cockpit CMS versionCheck the version file or composer.json in the Cockpit installation directory. Common locations include a version.php file, composer.json version field, or a /lib folder with version information.Affected if The installed version is 0.12.2 or any earlier version up to and including 0.12.2
-
Locate the config.yaml fileNavigate to the /config/config.yaml file within the Cockpit CMS installation directory. Verify this file exists and is readable.Affected if The config.yaml file exists and is accessible for parsing
-
Verify htaccess Handler is processing YAMLExamine the htaccess file and any PHP handler configuration that routes requests through the Spyc::YAMLLoad function when /config/config.yaml is accessed. Check if YAML parsing is triggered on user-controlled or external input.Affected if The htaccess Handler is configured to process config.yaml through Spyc::YAMLLoad without proper input sanitization
-
Check file system permissions on config filesReview file system permissions on the /config directory and config.yaml to determine if the web server user has read access to sensitive files outside the intended config scope.Affected if The web server process can read arbitrary files on the system due to overly permissive file access
You are affected if Cockpit CMS version 0.12.2 or earlier is installed and the htaccess Handler processes config.yaml through Spyc::YAMLLoad without proper input validation.
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 dataUpgrade Cockpit CMS to a version beyond 0.12.2 that addresses this vulnerability. If no patched version exists, implement strict input validation on YAML files and restrict file access permissions to prevent unauthorized file system access.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13533 — 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-13533 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