CVE-2026-56734

MEDIUMPre-NVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (31st percentile of EPSS-scored CVEs). 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, during federated authentication (OAuth/OIDC/SAML), a profile image URL from the external identity provider is fetched without verifying the target address. An actor who controls their profile at a connected provider may cause the server to connect to internal network locations. Response timing and error patterns differ between reachable and unreachable targets, allowing internal service probing. Worker processes may be blocked for several seconds per request. Requires a configured external authentication provider where the actor can modify their profile image URL. This issue is fixed in version 7.0.2.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100CISA SSVC

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%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 29, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
Patch available. Sources: github_commit, github.
github_commit

commit 1fae97d92496 (zammad/zammad)

Fix landed in zammad/zammad commit 1fae97d92496 — awaiting tagged release

https://github.com/zammad/zammad/commit/1fae97d92496a643ea1490fb17070881e4e091d5
github Patch Available

Avatar Image URL Server-Side Request Forwarding · Advisory · zammad/zammad · GitHub

https://github.com/zammad/zammad/security/advisories/GHSA-q3cr-3wq3-29hx

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 21× 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-10-04 12:48 UTCEG score recompute
  2. 2026-10-03 14:26 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEG score recompute
  4. 2026-10-02 17:56 UTCEPSS rescore
  5. 2026-10-02 15:53 UTCEG score recompute
  6. 2026-10-01 19:50 UTCEPSS rescore
  7. 2026-09-30 18:58 UTCEG score recompute
  8. 2026-09-30 15:03 UTCEPSS rescore
  9. 2026-09-29 20:31 UTCEG score recompute
  10. 2026-09-29 19:45 UTCEG score recompute
  11. 2026-09-29 15:22 UTCEPSS rescore
  12. 2026-09-29 13:24 UTCEG score recompute
  13. 2026-09-28 14:01 UTCEG score recompute
  14. 2026-09-28 13:51 UTCEPSS rescore
  15. 2026-09-27 15:34 UTCEG score recompute
  16. 2026-09-27 13:48 UTCEPSS rescore
  17. 2026-09-26 17:06 UTCEG score recompute
  18. 2026-09-26 15:59 UTCEPSS rescore
  19. 2026-09-25 18:38 UTCEG score recompute
  20. 2026-09-25 17:19 UTCEG score recompute
  21. 2026-09-25 17:19 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56734?
CVE-2026-56734 is a medium vulnerability published on September 25, 2026. Zammad is a web based open source helpdesk/customer support system. Prior to 7.0.2, during federated authentication (OAuth/OIDC/SAML), a profile image URL from the external identity provider is fetched without verifying the target address. An actor who controls their profile at a connected provider…
When was CVE-2026-56734 disclosed?
CVE-2026-56734 was first published on September 25, 2026, with the most recent update on September 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-56734 actively exploited?
CVE-2026-56734 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-56734?
CVE-2026-56734 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-56734?
A fix for CVE-2026-56734 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-56734?

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

Book a Demo →Browse All CVEs