# CVE-2026-13533: agentejo Cockpit CMS htaccess config.yaml YAMLLoad file access

> Remote attackers can access sensitive files or directories via the htaccess handler in Cockpit CMS if specific configuration settings are not properly secured.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-q4hh-wg87-823q

## What is CVE-2026-13533?

CVE-2026-13533 is a medium-severity path traversal vulnerability in agentejo Cockpit CMS, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A 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.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-425 (Direct Request)

## Which versions are affected by CVE-2026-13533?


## How do I fix CVE-2026-13533?

No fix has been published for CVE-2026-13533 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13533 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13533 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13533 and fix it if it is affected.

What it is: CVE-2026-13533 is a medium-severity path traversal vulnerability in agentejo Cockpit CMS, published on 29 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13533 exists.

Affected product: agentejo Cockpit CMS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13533/ (Markdown: https://insights.sbomify.com/CVE-2026-13533/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13533
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13533
- OSV: https://osv.dev/vulnerability/CVE-2026-13533

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13533/
Summaries are generated and may contain mistakes; the official description above is the record.