# CVE-2026-125758: Aptabase before commit 61d4c01 Authentication Bypass via Known Example AUTH_SECRET


- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 10 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-gc76-cqm4-vqcf, GHSA-q925-46h4-fq6w

## What is CVE-2026-125758?

CVE-2026-125758 is a critical vulnerability in aptabase, published on 10 Nov 2026. 

### Official description

Aptabase before commit 61d4c01 contains an authentication bypass vulnerability that allows unauthenticated attackers to forge sign-in links by using the publicly known example AUTH_SECRET. Attackers can enumerate registered e-mails via /api/_auth/signin, forge HS256 JWTs redeemed by /api/_auth/continue, impersonate users, export analytics data, and transfer app ownership.

Weakness: CWE-1188 (Initialization of a Resource with an Insecure Default)

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


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

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

## Is CVE-2026-125758 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125758 is a critical vulnerability in aptabase, published on 10 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125758 in the wild and no public exploit code.

Affected product: aptabase. 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-125758/ (Markdown: https://insights.sbomify.com/CVE-2026-125758/index.md)
```

## Sources

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

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