# CVE-2025-54305: Auth bypass in n/a

> Local attackers can bypass authentication and gain ionadmin privileges by spoofing localhost IP addresses in the Thermo Fisher Torrent Suite application.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Dec 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-rxh6-pq89-vv2f

## What is CVE-2025-54305?

CVE-2025-54305 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

An issue was discovered in the Thermo Fisher Torrent Suite Django application 5.18.1. One of the middlewares included in this application, LocalhostAuthMiddleware, authenticates users as ionadmin if the REMOTE_ADDR property in request.META is set to 127.0.0.1, to 127.0.1.1, or to ::1. Any user with local access to the server may bypass authentication.

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Thermofisher Torrent Suite Software.

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

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

## Is CVE-2025-54305 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-54303](https://insights.sbomify.com/CVE-2025-54303/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2025-54307](https://insights.sbomify.com/CVE-2025-54307/): Path traversal in n/a (high 8.8)
- [CVE-2025-54306](https://insights.sbomify.com/CVE-2025-54306/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54305 is a high-severity authentication bypass vulnerability in n/a, published on 4 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-54305 in the wild and no public exploit code.

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

## Sources

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

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