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

> Attackers can bypass OTP verification by replaying intercepted responses, though the vendor disputes this as intended behavior.

- **Severity:** Medium 4.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Sep 2025
- **Updated:** 16 Sep 2025
- **Also known as:** GHSA-6q6r-cf26-j7gh

## What is CVE-2025-56689?

CVE-2025-56689 is a medium-severity authentication bypass vulnerability in n/a, published on 3 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

One Identity by Quest Safeguard for Privileged Passwords Appliance 7.5.1.20903 is vulnerable to One Time Password (OTP)/Multifactor Authentication (MFA) bypass using response manipulation. An attacker who intercepts or captures a valid OTP response can bypass the OTP verification step by replaying the same response. NOTE: this is disputed by the Supplier because, by design, the product successfully authenticates a client that possesses a cookie whose validity time interval includes the current time, and thus authentication after any type of "interception" is not a violation of the security model. (The cookie has the HttpOnly attribute.)

Weakness: CWE-290 (Authentication Bypass by Spoofing)

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

It affects 1 product.


Products: Quest One Identity.

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

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

## Is CVE-2025-56689 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56689 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56689 is a medium-severity authentication bypass vulnerability in n/a, published on 3 Sep 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-56689 exists.

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

## Sources

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

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