# CVE-2026-13761: Denial of service in Pega Infinity

> Attackers can cause denial of service in Pega Platform by exploiting improper input validation in loop conditions.

- **Severity:** High 8.8 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-jrj4-4j46-4jjj

## What is CVE-2026-13761?

CVE-2026-13761 is a high-severity denial of service vulnerability in Pegasystems Pega Infinity, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-606 (Unchecked Input for Loop Condition)

## Which versions are affected by CVE-2026-13761?


## How do I fix CVE-2026-13761?

No fix has been published for CVE-2026-13761 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13761 being exploited?

There is no known exploitation of CVE-2026-13761 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13761 and fix it if it is affected.

What it is: CVE-2026-13761 is a high-severity denial of service vulnerability in Pegasystems Pega Infinity, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-13761 in the wild and no public exploit code.

Affected product: Pegasystems Pega Infinity. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-13761/ (Markdown: https://insights.sbomify.com/CVE-2026-13761/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13761
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13761
- OSV: https://osv.dev/vulnerability/CVE-2026-13761

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13761/
Summaries are generated and may contain mistakes; the official description above is the record.