# CVE-2025-64180: Manager-io/Manager: Complete Bypass of SSRF Protection via Time-of-Check Time-of-Use (TOCTOU)

> Attackers can bypass SSRF protections via a TOCTOU race condition to access internal network resources and cloud metadata endpoints.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Nov 2025
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-j2xj-xhph-p74j

## What is CVE-2025-64180?

CVE-2025-64180 is a critical server-side request forgery vulnerability in Manager-io Manager, published on 7 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Manager-io/Manager is accounting software. In Manager Desktop and Server versions 25.11.1.3085 and below, a critical vulnerability permits unauthorized access to internal network resources. The flaw lies in the fundamental design of the DNS validation mechanism. A Time-of-Check Time-of-Use (TOCTOU) condition that allows attackers to bypass network isolation and access internal services, cloud metadata endpoints, and protected network segments. The Desktop edition requires no authentication; the Server edition requires only standard authentication. This issue is fixed in version 25.11.1.3086.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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


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

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

## Is CVE-2025-64180 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-64180 is a critical server-side request forgery vulnerability in Manager-io Manager, published on 7 Nov 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-64180 in the wild and no public exploit code.

Affected product: Manager-io Manager. 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-2025-64180/ (Markdown: https://insights.sbomify.com/CVE-2025-64180/index.md)
```

## Sources

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

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