# CVE-2025-6737: Securden Unified PAM Shared SSH Key and Cloud Infrastructure

> Attackers can obtain shared authentication tokens to access the gateway server with low privileges due to multi-tenant infrastructure sharing.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **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-j677-558j-pgrq

## What is CVE-2025-6737?

CVE-2025-6737 is a high-severity 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

Securden’s Unified PAM Remote Vendor Gateway access portal shares infrastructure and access tokens across multiple tenants. A malicious actor can obtain authentication material and access the gateway server with low-privilege permissions.

Weakness: CWE-1391 (Use of Weak Credentials)

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


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

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

## Is CVE-2025-6737 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-6737 is a high-severity 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: There is no known exploitation of CVE-2025-6737 in the wild and no public exploit code.

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

## Sources

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

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