Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-13761 – Denial of Service via Unchecked Loop Condition – Pega Platform 7.1.0 through 25.1.2

Be the first to know when new zero-days emerge:

Summary

CVE-2026-13761 is a high-severity vulnerability in Pegasystems’ Pega Platform (Pega Infinity) caused by improper validation of inputs used in loop conditions (CWE-606: Unchecked Input for Loop Condition). An unauthenticated, network-based attacker can trigger excessive looping, leading to denial of service and integrity compromise on affected instances. The issue carries a CVSS base score of 8.8 and affects versions 7.1.0 through 25.1.2.

Technical details

  • Root cause: The application fails to properly validate attacker-controllable input that governs a loop’s termination condition, classified under CWE-606 (Unchecked Input for Loop Condition) / CAPEC-130 (Excessive Allocation).
  • Trigger conditions: An attacker supplies crafted input that is used to control loop iteration, causing excessive/uncontrolled looping within the platform.
  • Attack vector: Network-based; no authentication and no user interaction is required to exploit.
  • Impact: High impact to availability (denial of service via resource exhaustion from excessive looping) and high impact to integrity.

Affected software

  • Pegasystems Pega Platform (Pega Infinity), versions 7.1.0 through 25.1.2
  • Fixed in version 25.1.3

Severity

  • CVSS v4.0 Base Score: 8.8 (High)
  • Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:L
  • Network attack vector, low attack complexity, no privileges or user interaction required, high integrity and availability impact.

Mitigation and recommended actions

  • Immediate: Upgrade Pega Platform (Pega Infinity) to version 25.1.3 or later, as specified in Pegasystems’ security advisory.
  • If immediate patching is not possible: Restrict network exposure of Pega Platform instances to trusted networks, and consult Pegasystems’ official security advisory portal for any interim guidance or configuration-based mitigations specific to your deployed version.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge