CVE-2026-13533

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreHIGH confidence

Score 5.3 from GitHub Security Advisory published 2026-06-29. a secondary CVSS source baseline 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(high)
EG Risk
55(Attend)
EG Risk 55/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 29, 2026

Advisory Details (1)

Auto-updated Jun 29, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Cockpit CMS v1 Unauthenticated config.yaml Disclosure — CWE-552 (5.4k stars, unmaintained, 0day) · GitHub

https://gist.github.com/nov-1337/3eb0a06c602ced9c3b11b675b53947da

Vendor Advisories for CVE-2026-13533(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 13× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 14:13 UTCEPSS rescore
  2. 2026-07-27 13:08 UTCEG score recompute
  3. 2026-07-27 13:08 UTCGHSA enrichment
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-26 14:23 UTCEG score recompute
  7. 2026-07-26 14:22 UTCGHSA enrichment
  8. 2026-07-25 14:17 UTCEPSS rescore
  9. 2026-07-24 14:17 UTCEPSS rescore
  10. 2026-07-23 14:18 UTCEPSS rescore
  11. 2026-07-23 03:05 UTCEG score recompute
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:24 UTCEPSS rescore
  14. 2026-07-20 17:08 UTCEPSS rescore
  15. 2026-07-19 14:30 UTCEPSS rescore
  16. 2026-07-19 02:28 UTCEPSS rescore
  17. 2026-07-18 10:04 UTCEPSS rescore
  18. 2026-07-16 20:18 UTCGHSA enrichment
  19. 2026-07-16 17:02 UTCEPSS rescore
  20. 2026-07-15 22:02 UTCGHSA enrichment
  21. 2026-07-15 16:57 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 23:45 UTCGHSA enrichment
  24. 2026-07-14 01:30 UTCGHSA enrichment
  25. 2026-07-13 22:30 UTCEPSS rescore
Show 35 more
  1. 2026-07-13 06:12 UTCEPSS rescore
  2. 2026-07-13 03:15 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-12 04:58 UTCGHSA enrichment
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-11 06:43 UTCGHSA enrichment
  7. 2026-07-10 08:28 UTCGHSA enrichment
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 10:13 UTCGHSA enrichment
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-08 11:58 UTCGHSA enrichment
  13. 2026-07-07 13:46 UTCEPSS rescore
  14. 2026-07-07 13:43 UTCGHSA enrichment
  15. 2026-07-06 16:27 UTCEPSS rescore
  16. 2026-07-06 15:28 UTCGHSA enrichment
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 17:12 UTCGHSA enrichment
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 18:56 UTCGHSA enrichment
  22. 2026-07-03 20:40 UTCGHSA enrichment
  23. 2026-07-02 22:24 UTCGHSA enrichment
  24. 2026-07-02 00:09 UTCGHSA enrichment
  25. 2026-07-01 15:06 UTCEPSS rescore
  26. 2026-07-01 15:06 UTCEPSS rescore
  27. 2026-07-01 01:54 UTCGHSA enrichment
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-30 03:38 UTCGHSA enrichment
  30. 2026-06-29 17:26 UTCNVD updateCVSS v4 → 5.5
  31. 2026-06-29 16:13 UTCMITRE cvelistV5CVSS v4 → 6.9
  32. 2026-06-29 14:06 UTCEPSS rescore
  33. 2026-06-29 08:04 UTCNVD updateCVSS v4 → 5.5
  34. 2026-06-29 05:19 UTCEG score recompute
  35. 2026-06-29 05:17 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13533?
CVE-2026-13533 is a medium vulnerability published on June 29, 2026. 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…
When was CVE-2026-13533 disclosed?
CVE-2026-13533 was first published in the National Vulnerability Database on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13533 actively exploited?
CVE-2026-13533 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 79.2% of all scored CVEs.
What is the CVSS score of CVE-2026-13533?
CVE-2026-13533 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-13533?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13533, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-13533

Explore →

Is Your Infrastructure Affected by CVE-2026-13533?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs