CVE-2026-90910

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

GHSA-q532-rv5p-f5vr ↗EUVD-2026-104165 ↗

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

description

Apache Answer through 2.0.2 does not properly enforce access controls for reaction API operations on restricted content. An unauthorized user may view associated reaction metadata or add and remove their own reactions when restricted content is present.

mitigation

Upgrade Apache Answer to version 2.0.3 or later. Restrict access to the reaction API until the update is deployed.

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.64%49th percentile
agent run time
13m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 09:35Z
Δ 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-19 09:35Z
    ghsa: trigger signal, started the run
  2. 2026-10-19 09:35Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2099",
  "cve_id": "CVE-2026-90910",
  "display_id": "CVE-2026-90910",
  "ghsa_id": "GHSA-q532-rv5p-f5vr",
  "euvd_id": "EUVD-2026-104165",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Missing authentication in Apache Answer reaction API",
  "summary": "Apache Answer through 2.0.2 does not properly enforce access controls for reaction API operations on restricted content. An unauthorized user may view associated reaction metadata or add and remove their own reactions when restricted content is present.",
  "mitigation": "Upgrade Apache Answer to version 2.0.3 or later. Restrict access to the reaction API until the update is deployed.",
  "vendor": "Apache Software Foundation",
  "product": "Apache Answer",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2.0.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Apache Answer",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0064,
  "epss_percentile": 0.4963,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 12.662122483333333,
  "t0_at": "2026-10-19T09:35:54.679000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-19T09:35:54.679000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T09:35:54.679000+00:00",
      "url": "https://github.com/advisories/GHSA-q532-rv5p-f5vr"
    }
  }
}

published 2026-10-20 00:30Z
last change 2026-10-21 16:41Z

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.