CVE-2026-121939

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

GHSA-3962-28xr-cf4g ↗EUVD-2026-116896 ↗

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.
David-Crty Databasement < 1.10.9
fixed in 1.10.9
CWE-290 Authentication Bypass by Spoofing
ETK-2026-3500Zero's internal tracking ID, independent of the CVE number., permanent identifier
24msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h15m
0
+2h
+6h
+8h
+10h
+12h

description

Databasement versions before 1.10.9 can associate an OIDC identity with a local account without confirming that the identity provider verified its email address. An attacker who can create an identity-provider account using a target user's unverified email may gain access as that local user, potentially including an administrative user.

mitigation

Upgrade Databasement to version 1.10.9 or later. Until upgraded, disable or restrict OIDC login paths that permit accounts with unverified email addresses.

fixed in 1.10.9

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.
contextual
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
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 12:31Z
Δ 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

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-04 12:31Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3500",
  "cve_id": "CVE-2026-121939",
  "display_id": "CVE-2026-121939",
  "ghsa_id": "GHSA-3962-28xr-cf4g",
  "euvd_id": "EUVD-2026-116896",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OIDC email-verification authentication bypass in Databasement",
  "summary": "Databasement versions before 1.10.9 can associate an OIDC identity with a local account without confirming that the identity provider verified its email address. An attacker who can create an identity-provider account using a target user's unverified email may gain access as that local user, potentially including an administrative user.",
  "mitigation": "Upgrade Databasement to version 1.10.9 or later. Until upgraded, disable or restrict OIDC login paths that permit accounts with unverified email addresses.",
  "vendor": "David-Crty",
  "product": "Databasement",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 1.10.9"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "1.10.9"
      ],
      "package_name": "Databasement",
      "purl": null
    }
  ],
  "cwes": [
    290
  ],
  "cvss_score": 9.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.5248854,
  "t0_at": "2026-11-04T12:31:18.485000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-04T12:31:18.485000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T12:31:18.485000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-121939"
    }
  }
}

published 2026-11-04 12:55Z
last change 2026-11-04 16:46Z

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.