CVE-2026-119662 Songloft 2.9.0 before 2.13.6 Hardcoded Admin Credentials in Embedded Backend
High 8.7
Published
Updated
Check this codebase for CVE-2026-119662 and fix it if it is affected.
What it is: CVE-2026-119662 is a high-severity vulnerability in songloft-org songloft, published on 30 Oct 2026.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119662 exists.
Affected product: songloft-org songloft. 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-119662/ (Markdown: https://insights.sbomify.com/CVE-2026-119662/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119662?
CVE-2026-119662 is a high-severity vulnerability in songloft-org songloft, published on 30 Oct 2026.
Official description
Songloft 2.9.0 before 2.13.6 contains a hardcoded credentials vulnerability that allows adjacent network attackers to authenticate as administrator using the fixed admin/admin pair. Attackers on the same network can log in via the /api/v1/auth/login endpoint to modify library and configuration settings and install JavaScript plugins running in QuickJS.
Weakness: CWE-798
Which versions are affected by CVE-2026-119662?
How do I fix CVE-2026-119662?
No fix has been published for CVE-2026-119662 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119662 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119662 exists.
Sources
Also known as GHSA-642p-47qh-4hhp.