# CVE-2026-71801: Hardcoded credentials in n/a

> Remote attackers can bypass authentication and gain full administrative access to SPMS Server backend APIs due to a hardcoded default access token secret.

- **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:** 9 Sep 2026
- **Updated:** 14 Sep 2026
- **Also known as:** GHSA-xvj8-284g-wf2v

## What is CVE-2026-71801?

CVE-2026-71801 is a critical vulnerability in n/a, published on 9 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in s-pms SPMS-Server through v1.0. The application contains a hardcoded default access token secret within its core configuration file, which is not overridden or removed in the production environment profile. A remote, unauthenticated attacker can locally forge valid administrative session tokens to completely bypass the authentication mechanism gaining full unauthorized access to protected backend APIs.

Weakness: CWE-798 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2026-71801?


## How do I fix CVE-2026-71801?

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

## Is CVE-2026-71801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-71801 and fix it if it is affected.

What it is: CVE-2026-71801 is a critical vulnerability in n/a, published on 9 Sep 2026. 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-2026-71801 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-2026-71801/ (Markdown: https://insights.sbomify.com/CVE-2026-71801/index.md)
```

## Sources

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

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