CVE-2026-22674

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreHIGH confidence

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

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

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

Hashgraph Guardian through 3.6.0, fixed in commit ba8c566, contains a stored cross-site scripting vulnerability that allows authenticated users with the STANDARD_REGISTRY role to inject malicious scripts by submitting a crafted companyName value via the branding configuration API endpoint. Attackers can exploit the unsanitized innerHTML assignment in the branding service to execute arbitrary JavaScript in the browser of every authenticated user on every page load.

CVSS v3
4.8
EG Score
4.8(high)
EPSS
7.5%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 23, 2026

Advisory Details (3)

Auto-updated Jun 18, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Hashgraph Guardian Stored XSS via branding companyName field | Advisories | VulnCheck

https://www.vulncheck.com/advisories/hashgraph-guardian-stored-xss-via-branding-companyname-field
github_pr

fix: prevent stored XSS in branding company name (CVE-2026-22674)

Fix merged in hashgraph/guardian PR #6190 on 2026-06-15 — awaiting tagged release

https://github.com/hashgraph/guardian/pull/6190
github_commit

commit ba8c56680784 (hashgraph/guardian)

Fix landed in hashgraph/guardian commit ba8c56680784 — awaiting tagged release

https://github.com/hashgraph/guardian/commit/ba8c566807848cf84360716438056d8d8d2c8362

Vendor Advisories for CVE-2026-22674(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 23× in last 7d / 59× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-06 12:46 UTCEG score recompute
  4. 2026-07-06 12:46 UTCGHSA enrichment
  5. 2026-07-06 02:23 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 12:00 UTCEG score recompute
  8. 2026-07-05 12:00 UTCGHSA enrichment
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 11:14 UTCEG score recompute
  11. 2026-07-04 11:14 UTCGHSA enrichment
  12. 2026-07-04 06:31 UTCEPSS rescore
  13. 2026-07-04 06:31 UTCEPSS rescore
  14. 2026-07-03 10:26 UTCEG score recompute
  15. 2026-07-03 10:26 UTCGHSA enrichment
  16. 2026-07-02 09:36 UTCEG score recompute
  17. 2026-07-02 09:36 UTCGHSA enrichment
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-07-01 08:50 UTCEG score recompute
  21. 2026-07-01 08:50 UTCGHSA enrichment
  22. 2026-06-30 23:22 UTCEPSS rescore
  23. 2026-06-30 23:22 UTCEPSS rescore
  24. 2026-06-30 08:04 UTCEG score recompute
  25. 2026-06-30 08:04 UTCGHSA enrichment
Show 34 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 07:18 UTCEG score recompute
  3. 2026-06-29 07:18 UTCGHSA enrichment
  4. 2026-06-28 14:07 UTCEPSS rescore
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 06:33 UTCEG score recompute
  7. 2026-06-28 06:33 UTCGHSA enrichment
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-28 04:56 UTCEPSS rescore
  10. 2026-06-27 05:48 UTCEG score recompute
  11. 2026-06-27 05:48 UTCGHSA enrichment
  12. 2026-06-27 03:08 UTCEPSS rescore
  13. 2026-06-26 05:02 UTCEG score recompute
  14. 2026-06-26 05:02 UTCGHSA enrichment
  15. 2026-06-25 13:49 UTCEPSS rescore
  16. 2026-06-25 13:49 UTCEPSS rescore
  17. 2026-06-25 04:16 UTCEG score recompute
  18. 2026-06-25 04:16 UTCGHSA enrichment
  19. 2026-06-24 14:05 UTCEPSS rescore
  20. 2026-06-24 14:05 UTCEPSS rescore
  21. 2026-06-24 03:27 UTCEG score recompute
  22. 2026-06-24 03:27 UTCGHSA enrichment
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-23 21:32 UTCEPSS rescore
  25. 2026-06-23 02:42 UTCEG score recompute
  26. 2026-06-23 02:42 UTCGHSA enrichment
  27. 2026-06-22 01:50 UTCEG score recompute
  28. 2026-06-22 01:50 UTCGHSA enrichment
  29. 2026-06-21 01:03 UTCEG score recompute
  30. 2026-06-21 01:03 UTCGHSA enrichment
  31. 2026-06-20 00:14 UTCEG score recompute
  32. 2026-06-20 00:13 UTCGHSA enrichment
  33. 2026-06-18 23:24 UTCEG score recompute
  34. 2026-06-18 23:22 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-22674?
CVE-2026-22674 is a medium vulnerability published on June 18, 2026. Hashgraph Guardian through 3.6.0, fixed in commit ba8c566, contains a stored cross-site scripting vulnerability that allows authenticated users with the STANDARD_REGISTRY role to inject malicious scripts by submitting a crafted companyName value via the branding configuration API endpoint.…
When was CVE-2026-22674 disclosed?
CVE-2026-22674 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-22674 actively exploited?
CVE-2026-22674 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-22674?
CVE-2026-22674 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-22674?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-22674, 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-22674

Explore →

Is Your Infrastructure Affected by CVE-2026-22674?

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

Start Free Scan →Browse All CVEs