CVE-2026-92120

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

GHSA-ccrf-jfj2-x65f ↗EUVD-2026-97832 ↗

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.
Apache Software Foundation Apache Allura <= 1.21.0
CWE-294 Authentication Bypass by Capture-replay
ETK-2026-2007Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 09h 41msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+143h57m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Allura versions through 1.21.0 are affected by an OAuth 1 request replay vulnerability. An unauthenticated attacker may be able to replay OAuth 1 requests against an affected instance; the advisory provides no further deployment-specific preconditions.

mitigation

Upgrade Apache Allura to version 1.22.0 or later. Until upgraded, reduce exposure to OAuth 1 request handling where operationally feasible.

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.
0.27%18th percentile
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 20:08Z
Δ 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: an exploit technique exists, 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-10-12 20:08Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2007",
  "cve_id": "CVE-2026-92120",
  "display_id": "CVE-2026-92120",
  "ghsa_id": "GHSA-ccrf-jfj2-x65f",
  "euvd_id": "EUVD-2026-97832",
  "status": "published",
  "anchor_state": "anchored",
  "title": "OAuth 1 request replay in Apache Allura",
  "summary": "Apache Allura versions through 1.21.0 are affected by an OAuth 1 request replay vulnerability. An unauthenticated attacker may be able to replay OAuth 1 requests against an affected instance; the advisory provides no further deployment-specific preconditions.",
  "mitigation": "Upgrade Apache Allura to version 1.22.0 or later. Until upgraded, reduce exposure to OAuth 1 request handling where operationally feasible.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Allura",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 1.21.0"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Allura",
      "purl": null
    }
  ],
  "cwes": [
    294
  ],
  "cvss_score": 9.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0027,
  "epss_percentile": 0.1861,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.144021283333334,
  "t0_at": "2026-10-12T20:08:15.489000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T20:08:15.489000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T20:08:15.489000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-92120"
    }
  }
}

published 2026-10-18 19:42Z
last change 2026-10-21 04:45Z

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.