CVE-2026-74760

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

GHSA-86rg-2xqg-4p5p ↗EUVD-2026-114874 ↗

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.
Google-Auth >= 0.11, <= 0.12
CWE-346 Origin Validation Error
ETK-2026-3239Zero's internal tracking ID, independent of the CVE number., permanent identifier
1h 45msince last run
35mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h04m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Google::Auth versions 0.11 through 0.12 for Perl are affected in gcloud-auth login and application-default login flows. A local attacker able to reach the loopback callback while a user is authenticating can cause the CLI to retain credentials for the attacker’s account, making later tool actions run under that account.

mitigation

Do not perform affected login flows on shared or untrusted systems, and restrict local access while authentication is in progress. Review and replace stored credentials after suspected exposure; no fixed version is recorded.

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.
–
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
35m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-01 16:43Z
Δ 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-01 16:43Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-3239",
  "cve_id": "CVE-2026-74760",
  "display_id": "CVE-2026-74760",
  "ghsa_id": "GHSA-86rg-2xqg-4p5p",
  "euvd_id": "EUVD-2026-114874",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OAuth state validation flaw in Google-Auth",
  "summary": "Google::Auth versions 0.11 through 0.12 for Perl are affected in gcloud-auth login and application-default login flows. A local attacker able to reach the loopback callback while a user is authenticating can cause the CLI to retain credentials for the attacker’s account, making later tool actions run under that account.",
  "mitigation": "Do not perform affected login flows on shared or untrusted systems, and restrict local access while authentication is in progress. Review and replace stored credentials after suspected exposure; no fixed version is recorded.",
  "vendor": null,
  "product": "Google-Auth",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0.11, <= 0.12"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Google-Auth",
      "purl": null
    }
  ],
  "cwes": [
    346
  ],
  "cvss_score": null,
  "cvss_src": null,
  "cvss_vector": null,
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 35.00597905,
  "t0_at": "2026-11-01T16:43:34.512000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-01T16:43:34.512000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-01T16:43:34.512000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-74760"
    }
  }
}

published 2026-11-01 17:12Z
last change 2026-11-01 19: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.