CVE-2025-70041 Hardcoded credentials in n/a
Critical 9.8
Published
Updated
Check this codebase for CVE-2025-70041 and fix it if it is affected.
What it is: CVE-2025-70041 is a critical vulnerability in n/a, published on 11 Mar 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-70041 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-70041/ (Markdown: https://insights.sbomify.com/CVE-2025-70041/index.md)
Hard-coded password in ThermaKube master allows attackers to bypass authentication and gain unauthorized access.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-70041?
CVE-2025-70041 is a critical vulnerability in n/a, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
An issue pertaining to CWE-259: Use of Hard-coded Password was discovered in oslabs-beta ThermaKube master.
Weakness: CWE-259
Which versions are affected by CVE-2025-70041?
How do I fix CVE-2025-70041?
No fix has been published for CVE-2025-70041 yet. Limit exposure of the affected software until one is available.
Is CVE-2025-70041 being exploited?
There is no known exploitation of CVE-2025-70041 in the wild and no public exploit code.
Sources
Also known as GHSA-6f94-497c-p96p.