CVE-2026-92119

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

GHSA-fc7h-2757-8pc7 ↗EUVD-2026-97831 ↗

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
ETK-2026-2008Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 23h 15msince last run
30mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+144h16m
0
+2h
+4h
+6h
+8h
+10h

description

Apache Allura through version 1.21.0 is affected by a mass-assignment flaw in its REST API. An unauthenticated remote attacker may be able to modify unintended application data through the API; the evidence does not identify the specific fields or endpoints involved.

mitigation

Upgrade Apache Allura to version 1.22.0 or later. Until the upgrade is complete, restrict access to the REST API to trusted users and networks where 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.30%21st percentile
agent run time
30m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 20:06Z
Δ 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:06Z
    ghsa: trigger signal, started the run
  2. 2026-10-12 20:06Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2008",
  "cve_id": "CVE-2026-92119",
  "display_id": "CVE-2026-92119",
  "ghsa_id": "GHSA-fc7h-2757-8pc7",
  "euvd_id": "EUVD-2026-97831",
  "status": "published",
  "anchor_state": "anchored",
  "title": "REST API mass assignment in Apache Allura",
  "summary": "Apache Allura through version 1.21.0 is affected by a mass-assignment flaw in its REST API. An unauthenticated remote attacker may be able to modify unintended application data through the API; the evidence does not identify the specific fields or endpoints involved.",
  "mitigation": "Upgrade Apache Allura to version 1.22.0 or later. Until the upgrade is complete, restrict access to the REST API to trusted users and networks where 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": null,
  "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.003,
  "epss_percentile": 0.2155,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 29.724507233333334,
  "t0_at": "2026-10-12T20:06:52.868000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-12T20:06:52.868000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T20:06:52.868000+00:00",
      "url": "https://github.com/advisories/GHSA-fc7h-2757-8pc7"
    }
  }
}

published 2026-10-18 19:53Z
last change 2026-10-21 18:49Z

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.