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

> Attackers can bypass authentication to access web application functionality via proxy requests in Blue Access Cobalt.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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:** 6 Jan 2026
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-99f8-h8gr-45gh

## What is CVE-2025-60534?

CVE-2025-60534 is a critical authentication bypass vulnerability in n/a, published on 6 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Blue Access Cobalt v02.000.195 suffers from an authentication bypass vulnerability, which allows an attacker to selectively proxy requests in order to operate functionality on the web application without the need to authenticate with legitimate credentials.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Blueaccesstech Cobalt X1.

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

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

## Is CVE-2025-60534 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60534 is a critical authentication bypass vulnerability in n/a, published on 6 Jan 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-2025-60534 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-60534/ (Markdown: https://insights.sbomify.com/CVE-2025-60534/index.md)
```

## Sources

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

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