# CVE-2025-53118: Securden Unified PAM Authentication Bypass

> Unauthenticated attackers can bypass authentication to access administrator backup functions, compromising stored passwords, secrets, and session tokens.

- **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:** 25 Aug 2025
- **Updated:** 25 Aug 2025
- **Also known as:** GHSA-fq2g-f63j-9x36

## What is CVE-2025-53118?

CVE-2025-53118 is a critical authentication bypass vulnerability in Securden Unified PAM, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists which allows an unauthenticated attacker to control administrator backup functions, leading to compromise of passwords, secrets, and application session tokens stored by the Unified PAM.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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


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

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

## Is CVE-2025-53118 being exploited?

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

Public exploit code:

- Securden Unified PAM - Authentication Bypass (nuclei): http/cves/2025/CVE-2025-53118.yaml

## Fix prompt for AI coding agents

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

What it is: CVE-2025-53118 is a critical authentication bypass vulnerability in Securden Unified PAM, published on 25 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53118 exists.

Affected product: Securden Unified PAM. 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-53118/ (Markdown: https://insights.sbomify.com/CVE-2025-53118/index.md)
```

## Sources

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

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