CVE-2026-13761

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-67718 (ENISA EUVD) · GHSA-jrj4-4j46-4jjj (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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

The CVE record's description, written by its CNA (Pegasystems Inc.), states the affected versions: "Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive loopi…" No release containing a fix is confirmed on record.

Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
55
EG Risk 55/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
36th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 28, 2026

Last Modified

September 8, 2026

Vendor Advisories for CVE-2026-13761(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 10× in last 7d / 76× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 190 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  2. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
  3. 2026-10-25 14:48 UTCEG score recompute
  4. 2026-10-25 00:34 UTCEG score recompute
  5. 2026-10-25 00:34 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  6. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  7. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  8. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  9. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-20 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  11. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  12. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-18 05:03 UTCEG score recompute
  14. 2026-10-17 18:31 UTCEG score recompute
  15. 2026-10-17 18:30 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  16. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  18. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  19. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  20. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-10-12 16:34 UTCEG score recompute
  22. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  23. 2026-10-11 20:11 UTCEG score recompute
  24. 2026-10-11 18:23 UTCEG score recompute
  25. 2026-10-11 14:56 UTCEG score recompute
Show 75 more
  1. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  2. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  3. 2026-10-10 12:26 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  4. 2026-10-10 00:55 UTCEG score recompute
  5. 2026-10-10 00:55 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  6. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  7. 2026-10-09 02:42 UTCEG score recompute
  8. 2026-10-09 02:42 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  9. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  10. 2026-10-08 00:53 UTCEG score recompute
  11. 2026-10-08 00:53 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  12. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  13. 2026-10-07 06:43 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  14. 2026-10-06 19:12 UTCEG score recompute
  15. 2026-10-06 19:12 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  16. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  17. 2026-10-06 07:28 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  18. 2026-10-05 18:37 UTCEG score recompute
  19. 2026-10-05 18:37 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  20. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  21. 2026-10-05 07:07 UTCEG score recompute
  22. 2026-10-05 07:07 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  23. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  24. 2026-10-04 19:36 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  25. 2026-10-04 05:21 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  26. 2026-10-03 17:51 UTCEG score recompute
  27. 2026-10-03 17:51 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  28. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  29. 2026-10-03 06:21 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  30. 2026-10-02 18:50 UTCEG score recompute
  31. 2026-10-02 18:50 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  32. 2026-10-02 07:19 UTCEG score recompute
  33. 2026-10-02 07:19 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  34. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  35. 2026-10-01 19:49 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  36. 2026-10-01 07:20 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  37. 2026-09-30 19:49 UTCEG score recompute
  38. 2026-09-30 19:49 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  39. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  40. 2026-09-30 03:50 UTCEG score recompute
  41. 2026-09-30 03:50 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  42. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  43. 2026-09-29 08:39 UTCEG score recompute
  44. 2026-09-29 08:39 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  45. 2026-09-28 21:09 UTCEG score recompute
  46. 2026-09-28 21:09 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  47. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  48. 2026-09-28 07:03 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  49. 2026-09-27 19:28 UTCEG score recompute
  50. 2026-09-27 19:28 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  51. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  52. 2026-09-27 07:55 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  53. 2026-09-26 20:25 UTCEG score recompute
  54. 2026-09-26 20:25 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  55. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 15th percentile
  56. 2026-09-26 08:42 UTCEG score recompute
  57. 2026-09-26 08:42 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  58. 2026-09-25 06:24 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  59. 2026-09-24 18:53 UTCEG score recompute
  60. 2026-09-24 18:53 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  61. 2026-09-24 07:22 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  62. 2026-09-23 19:52 UTCEG score recompute
  63. 2026-09-23 19:52 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  64. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  65. 2026-09-23 06:59 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  66. 2026-09-22 19:28 UTCEG score recompute
  67. 2026-09-22 19:28 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  68. 2026-09-22 07:58 UTCEG score recompute
  69. 2026-09-22 07:57 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  70. 2026-09-21 20:27 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  71. 2026-09-21 08:55 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  72. 2026-09-20 21:25 UTCEG score recompute
  73. 2026-09-20 21:25 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH
  74. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  75. 2026-09-20 09:54 UTCGHSA enrichmentGHSA-jrj4-4j46-4jjj · GitHub severity HIGH

Frequently asked(5)

What is CVE-2026-13761?
CVE-2026-13761 is a high-severity vulnerability; its CVE record was published on August 28, 2026. Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.
When was CVE-2026-13761 made public?
CVE-2026-13761 was made public on August 28, 2026: that is the date its CVE record's CNA, Pegasystems Inc., gives for when the vulnerability was made public. The CVE record itself was published on August 28, 2026. EchelonGraph's copy of the record carries a last-modified date of September 8, 2026; the record at its source may have been updated since.
Is CVE-2026-13761 actively exploited?
CVE-2026-13761 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (36th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13761?
CVE-2026-13761 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-13761?
No fix for CVE-2026-13761 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The CVE record's description, written by its CNA (Pegasystems Inc.), states the affected versions: "Pega Platform versions 7.1.0 through 25.1.2 are affected by an improper validation of inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive loopi…" No release containing a fix is confirmed on record. The vendor advisories EchelonGraph has for CVE-2026-13761 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-13761?

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