CVE-2026-13229

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: Elevated riskExposed: 0

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

Zammad 7.1.0 contains an authenticated improper authorization vulnerability in the ticket article attachment cloning endpoint.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
48(Track)
EG Risk 48/100SSVC: Track

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
Severity71% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 4, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated Aug 4, 2026
Patch available. Sources: github.
github Patch Available

Missing authorization on ticket attachment download · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-374g-4f73-g7m7
generic

Zammad 7.0.1 - Improper authorization in ticket article attachment cloning | Fluid Attacks

https://fluidattacks.com/es/advisories/chicago

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 51× 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-08-30 01:21 UTCEPSS rescore
  2. 2026-08-29 21:46 UTCEG score recompute
  3. 2026-08-28 21:40 UTCEPSS rescore
  4. 2026-08-27 22:21 UTCEG score recompute
  5. 2026-08-27 14:24 UTCEPSS rescore
  6. 2026-08-26 22:32 UTCEG score recompute
  7. 2026-08-25 22:41 UTCEG score recompute
  8. 2026-08-25 13:48 UTCEPSS rescore
  9. 2026-08-24 22:52 UTCEG score recompute
  10. 2026-08-24 10:57 UTCEG score recompute
  11. 2026-08-23 11:05 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 11:16 UTCEG score recompute
  14. 2026-08-21 23:48 UTCEPSS rescore
  15. 2026-08-20 23:00 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-19 23:11 UTCEG score recompute
  18. 2026-08-19 17:03 UTCEPSS rescore
  19. 2026-08-18 23:19 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 23:31 UTCEG score recompute
  22. 2026-08-16 23:42 UTCEG score recompute
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 11:47 UTCEG score recompute
  25. 2026-08-16 02:14 UTCEPSS rescore
Show 26 more
  1. 2026-08-15 11:58 UTCEG score recompute
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 00:14 UTCEG score recompute
  4. 2026-08-13 22:00 UTCEPSS rescore
  5. 2026-08-13 00:24 UTCEG score recompute
  6. 2026-08-12 13:50 UTCEPSS rescore
  7. 2026-08-12 00:35 UTCEG score recompute
  8. 2026-08-11 13:42 UTCEPSS rescore
  9. 2026-08-11 00:47 UTCEG score recompute
  10. 2026-08-10 23:59 UTCEPSS rescore
  11. 2026-08-10 00:58 UTCEG score recompute
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-09 01:10 UTCEG score recompute
  14. 2026-08-08 16:37 UTCEPSS rescore
  15. 2026-08-08 01:20 UTCEG score recompute
  16. 2026-08-07 13:26 UTCEG score recompute
  17. 2026-08-07 13:13 UTCEG score recompute
  18. 2026-08-06 21:30 UTCEG score recompute
  19. 2026-08-06 13:46 UTCEPSS rescore
  20. 2026-08-05 21:41 UTCEG score recompute
  21. 2026-08-05 19:17 UTCEPSS rescore
  22. 2026-08-04 21:32 UTCEG score recompute
  23. 2026-08-04 21:13 UTCEG score recompute
  24. 2026-08-04 19:25 UTCEG score recompute
  25. 2026-08-04 18:21 UTCEG score recompute
  26. 2026-08-04 18:20 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-13229?
CVE-2026-13229 is a high vulnerability published on August 4, 2026. Zammad 7.1.0 contains an authenticated improper authorization vulnerability in the ticket article attachment cloning endpoint.
When was CVE-2026-13229 disclosed?
CVE-2026-13229 was first published in the National Vulnerability Database on August 4, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13229 actively exploited?
CVE-2026-13229 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 84.3% of all scored CVEs.
What is the CVSS score of CVE-2026-13229?
CVE-2026-13229 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-13229?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13229, 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-13229

Explore →

Is Your Infrastructure Affected by CVE-2026-13229?

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

Start Free Scan →Browse All CVEs