CVE-2026-125758

waiting for further signalsZero needs more public information before it can validate it.

GHSA-gc76-cqm4-vqcf ↗EUVD-2026-121241 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
aptabase main before 61d4c01
fixed in main from 61d4c01
CWE-1188 Initialization of a Resource with an Insecure Default
ETK-2026-4070Zero's internal tracking ID, independent of the CVE number., permanent identifier
13h 30msince last run
1h 35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h07m
0
+4h
+6h
+8h
+10h
+12h

description

Aptabase versions before commit 61d4c01298a706d575265461ac07bb956ca7b8d2 are affected by an authentication bypass. An unauthenticated attacker can impersonate users and access analytics data or transfer application ownership when the deployment uses the publicly known example AUTH_SECRET.

mitigation

Upgrade Aptabase to commit 61d4c01298a706d575265461ac07bb956ca7b8d2 or later. Replace any example AUTH_SECRET in deployed configurations with a unique secret.

fixed in main from 61d4c01

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
–
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
1h 35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-10 15:22Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-10 15:22Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-125758

{
  "etk_id": "ETK-2026-4070",
  "cve_id": "CVE-2026-125758",
  "display_id": "CVE-2026-125758",
  "ghsa_id": "GHSA-gc76-cqm4-vqcf",
  "euvd_id": "EUVD-2026-121241",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Aptabase",
  "summary": "Aptabase versions before commit 61d4c01298a706d575265461ac07bb956ca7b8d2 are affected by an authentication bypass. An unauthenticated attacker can impersonate users and access analytics data or transfer application ownership when the deployment uses the publicly known example AUTH_SECRET.",
  "mitigation": "Upgrade Aptabase to commit 61d4c01298a706d575265461ac07bb956ca7b8d2 or later. Replace any example AUTH_SECRET in deployed configurations with a unique secret.",
  "vendor": "aptabase",
  "product": "aptabase",
  "affected": [
    {
      "affected_notes": [
        "main before 61d4c01"
      ],
      "affected_ranges": [],
      "ecosystem": "other",
      "fixed_versions": [
        "main from 61d4c01"
      ],
      "package_name": "ghcr.io/aptabase/aptabase",
      "purl": null
    }
  ],
  "cwes": [
    1188
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_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",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 95.21923925,
  "t0_at": "2026-11-10T15:22:52.231000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-10T15:22:52.231000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-10T15:22:52.231000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-125758"
    }
  }
}

published 2026-11-10 15:54Z
last change 2026-11-11 05:12Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.