CVE-2026-115770

validatedZero produced an exploit or a check.

GHSA-rm8c-2cv8-jwf6 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).−98dkevAttacks confirmed in the real world.
go:github.com/pocket-id/pocket-id/backend >= v2.2.0
fixed in v2.12.0
CWE-345 Insufficient Verification of Data Authenticity
ETK-2026-3550Zero's internal tracking ID, independent of the CVE number., permanent identifier
pkg:golang/github.com/pocket-id/pocket-id/backend
+47mTTV
11mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = cve.org publication
public poc−3.2motrigger signal (cve.org) +0mocheck available+0.0moagent stopped
−3mo
−2mo
−1mo

description

Pocket ID backend versions 2.2.0 through before 2.12.0 can mark a changed account email address as verified using a token issued for the prior address. An authenticated user who can edit their own account can falsely obtain a verified-email claim for an unassigned address; impact on other applications requires them to trust that claim for email-based account matching or provisioning.

mitigation

Upgrade Pocket ID backend to v2.12.0. Until upgraded, restrict user email changes and avoid using verified email claims as the sole basis for account linking or provisioning.

fixed in v2.12.0

check
available
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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
11m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-04 22:32Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
−98d
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

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

  1. 2026-11-04 22:32Z
  2. 2026-11-04 22:32Z
  3. 2026-11-04 22:32Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-3550",
  "cve_id": "CVE-2026-115770",
  "display_id": "CVE-2026-115770",
  "ghsa_id": "GHSA-rm8c-2cv8-jwf6",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Email verification token binding flaw in Pocket ID backend",
  "summary": "Pocket ID backend versions 2.2.0 through before 2.12.0 can mark a changed account email address as verified using a token issued for the prior address. An authenticated user who can edit their own account can falsely obtain a verified-email claim for an unassigned address; impact on other applications requires them to trust that claim for email-based account matching or provisioning.",
  "mitigation": "Upgrade Pocket ID backend to v2.12.0. Until upgraded, restrict user email changes and avoid using verified email claims as the sole basis for account linking or provisioning.",
  "vendor": "go",
  "product": "go:github.com/pocket-id/pocket-id/backend",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= v2.2.0"
      ],
      "ecosystem": "go",
      "fixed_versions": [
        "v2.12.0"
      ],
      "package_name": "github.com/pocket-id/pocket-id/backend",
      "purl": "pkg:golang/github.com/pocket-id/pocket-id/backend"
    }
  ],
  "cwes": [
    345
  ],
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 11.37829685,
  "t0_at": "2026-11-04T22:32:18.097000+00:00",
  "signals": {
    "check": {
      "at": "2026-11-04T23:18:58.545482+00:00",
      "days": 0.0324125981712963,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T22:32:18.097000+00:00",
      "url": null
    },
    "public_poc": {
      "at": "2026-07-29T23:02:34+00:00",
      "days": -97.97898260416666,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T22:32:18.097000+00:00",
      "url": "https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6"
    },
    "trigger_signal": {
      "at": "2026-11-04T22:32:18.097000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-04T22:32:18.097000+00:00",
      "url": "https://github.com/pocket-id/pocket-id/security/advisories/GHSA-rm8c-2cv8-jwf6"
    }
  }
}

published 2026-11-04 23:07Z
last change 2026-11-05 00:05Z

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.