CVE-2026-5522

MEDIUMPre-NVD 6.76.7—
EchelonGraph scoreHIGH confidence

Score 6.7 from GitHub Security Advisory published 2026-09-04. a secondary CVSS source baseline 6.7; sources differ by 0.0.

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

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

IBM QRadar 7.5.0 through 7.5.0 UP15 Interim Fix 005 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.

CVSS v3
6.7
EG Score
6.7(high)
EG Risk
30(Track)
EG Risk 30/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
Severity67% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

September 4, 2026

Last Modified

September 8, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

Security Bulletin: QRadar contains hard-coded credentials

https://www.ibm.com/support/pages/node/7285277

Vendor Advisories for CVE-2026-5522(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-5522?
CVE-2026-5522 is a medium vulnerability published on September 4, 2026. IBM QRadar 7.5.0 through 7.5.0 UP15 Interim Fix 005 contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to external components, or encryption of internal data.
When was CVE-2026-5522 disclosed?
CVE-2026-5522 was first published in the National Vulnerability Database on September 4, 2026, with the most recent update on September 8, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-5522 actively exploited?
CVE-2026-5522 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 99.5% of all scored CVEs.
What is the CVSS score of CVE-2026-5522?
CVE-2026-5522 has a CVSS v3 base score of 6.7 (NVD).
How do I remediate CVE-2026-5522?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-5522, 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-5522

Explore →

Is Your Infrastructure Affected by CVE-2026-5522?

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

Start Free Scan →Browse All CVEs