CVE-2025-62180

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 88% 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
Trending — 3 sources updated this week
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

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

Pega Platform versions 8.3.0 through Infinity 25.1.2 are affected by an authorization weakness that may allow authenticated users to access certain additional data via crafted URLs.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
11.9%
KEV
Not listed

Published

June 23, 2026

Last Modified

June 23, 2026

Advisory Details (2)

Auto-updated Jun 23, 2026
No patch confirmed yet.
generic

Pega Security Advisory - H26 Vulnerability - Remediation Note | Support Center

https://support.pega.com/support-doc/pega-security-advisory-h26-vulnerability-remediation-note
generic

Pega Security Advisory I25 Vulnerability - Remediation Note | Support Center

https://support.pega.com/support-doc/pega-security-advisory-i25-vulnerability-remediation-note

Vendor Advisories for CVE-2025-62180(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 34× in last 7d / 70× 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 20:36 UTCEG score recompute
  2. 2026-07-06 20:35 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 07:27 UTCEG score recompute
  6. 2026-07-06 07:27 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 18:22 UTCEG score recompute
  10. 2026-07-05 18:21 UTCGHSA enrichment
  11. 2026-07-05 05:17 UTCEG score recompute
  12. 2026-07-05 05:17 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-05 02:30 UTCEPSS rescore
  15. 2026-07-04 16:10 UTCEG score recompute
  16. 2026-07-04 16:10 UTCGHSA enrichment
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-04 06:30 UTCEPSS rescore
  19. 2026-07-04 03:01 UTCEG score recompute
  20. 2026-07-04 03:00 UTCGHSA enrichment
  21. 2026-07-03 13:36 UTCEG score recompute
  22. 2026-07-03 13:36 UTCGHSA enrichment
  23. 2026-07-03 00:31 UTCEG score recompute
  24. 2026-07-03 00:31 UTCGHSA enrichment
  25. 2026-07-02 11:26 UTCEG score recompute
Show 45 more
  1. 2026-07-02 11:26 UTCGHSA enrichment
  2. 2026-07-01 22:21 UTCEG score recompute
  3. 2026-07-01 22:21 UTCGHSA enrichment
  4. 2026-07-01 15:06 UTCEPSS rescore
  5. 2026-07-01 15:06 UTCEPSS rescore
  6. 2026-07-01 08:50 UTCEG score recompute
  7. 2026-07-01 08:50 UTCGHSA enrichment
  8. 2026-06-30 19:45 UTCEG score recompute
  9. 2026-06-30 19:45 UTCGHSA enrichment
  10. 2026-06-30 06:40 UTCEG score recompute
  11. 2026-06-30 06:40 UTCGHSA enrichment
  12. 2026-06-29 17:35 UTCEG score recompute
  13. 2026-06-29 17:35 UTCGHSA enrichment
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-29 14:06 UTCEPSS rescore
  16. 2026-06-29 04:30 UTCEG score recompute
  17. 2026-06-29 04:30 UTCGHSA enrichment
  18. 2026-06-28 15:24 UTCEG score recompute
  19. 2026-06-28 15:24 UTCGHSA enrichment
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 14:07 UTCEPSS rescore
  22. 2026-06-28 04:56 UTCEPSS rescore
  23. 2026-06-28 04:55 UTCEPSS rescore
  24. 2026-06-28 02:20 UTCEG score recompute
  25. 2026-06-28 02:20 UTCGHSA enrichment
  26. 2026-06-27 13:16 UTCEG score recompute
  27. 2026-06-27 13:16 UTCGHSA enrichment
  28. 2026-06-27 03:08 UTCEPSS rescore
  29. 2026-06-27 00:11 UTCEG score recompute
  30. 2026-06-27 00:11 UTCGHSA enrichment
  31. 2026-06-26 11:05 UTCEG score recompute
  32. 2026-06-26 11:05 UTCGHSA enrichment
  33. 2026-06-25 21:29 UTCEG score recompute
  34. 2026-06-25 21:29 UTCGHSA enrichment
  35. 2026-06-25 13:49 UTCEPSS rescore
  36. 2026-06-25 08:24 UTCEG score recompute
  37. 2026-06-25 08:24 UTCGHSA enrichment
  38. 2026-06-24 19:19 UTCEG score recompute
  39. 2026-06-24 19:19 UTCGHSA enrichment
  40. 2026-06-24 14:04 UTCEPSS rescore
  41. 2026-06-24 14:04 UTCEPSS rescore
  42. 2026-06-24 04:52 UTCEG score recompute
  43. 2026-06-24 04:52 UTCGHSA enrichment
  44. 2026-06-23 15:47 UTCEG score recompute
  45. 2026-06-23 15:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-62180?
CVE-2025-62180 is a high vulnerability published on June 23, 2026. Pega Platform versions 8.3.0 through Infinity 25.1.2 are affected by an authorization weakness that may allow authenticated users to access certain additional data via crafted URLs.
When was CVE-2025-62180 disclosed?
CVE-2025-62180 was first published in the National Vulnerability Database 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-2025-62180 actively exploited?
CVE-2025-62180 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 11.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2025-62180?
CVE-2025-62180 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2025-62180?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-62180, 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-2025-62180

Explore →

Is Your Infrastructure Affected by CVE-2025-62180?

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

Start Free Scan →Browse All CVEs