# CVE-2025-32033: Apollo Router Operation Limits Vulnerable to Bypass via Integer Overflow

> An integer overflow in Apollo Router allows attackers to bypass operation limits, potentially enabling resource exhaustion or policy evasion.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-84m6-5m72-45fp

## What is CVE-2025-32033?

CVE-2025-32033 is a high-severity vulnerability in apollographql router, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Apollo Router Core is a configurable, high-performance graph router written in Rust to run a federated supergraph that uses Apollo Federation 2. Prior to 1.61.2 and 2.1.1, the operation limits plugin uses unsigned 32-bit integers to track limit counters (e.g. for a query's height). If a counter exceeded the maximum value for this data type (4,294,967,295), it wrapped around to 0, unintentionally allowing queries to bypass configured thresholds. This could occur for large queries if the payload limit were sufficiently increased, but could also occur for small queries with deeply nested and reused named fragments. This has been remediated in apollo-router versions 1.61.2 and 2.1.1.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2025-32033?

4 open source packages ship an affected version, including apollo-router.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `apollo-router` | crates.io | All versions | 1.61.2 |
| `apollo-router` | crates.io | All versions | 1.61.2 |
| `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.1.1 |
| `apollo-router` | crates.io | From 2.0.0-alpha.0 | 2.1.1 |

## How do I fix CVE-2025-32033?

Upgrade apollo-router to a fixed version for your release line: 1.61.2 or 2.1.1.

## Is CVE-2025-32033 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32033 and fix it if it is affected.

What it is: CVE-2025-32033 is a high-severity vulnerability in apollographql router, published on 7 Apr 2025. 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-2025-32033 in the wild and no public exploit code.

Affected packages and fixed versions:
- apollo-router (crates.io): affected all versions; fixed in 1.61.2
- apollo-router (crates.io): affected all versions; fixed in 1.61.2
- apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.1.1
- apollo-router (crates.io): affected from 2.0.0-alpha.0; fixed in 2.1.1

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-2025-32033/ (Markdown: https://insights.sbomify.com/CVE-2025-32033/index.md)
```

## Sources

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

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