← back to feed
CVE-2026-87744

CVE-2026-87744

validatedZero produced an exploit or a check.

GHSA-jh67-c59w-8h9x ↗EUVD-2026-97766 ↗

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).kevAttacks confirmed in the real world.
Red Hat Exploit Intelligence
CWE-425 Direct Request ('Forced Browsing')
ETK-2026-1408Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss9.1cna vendorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
+1h22mTTV
31mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+82magent stopped
0
+30min
+60min
+90min

description

Quarkus REST Data Panache generated endpoints can lose inherited class-level security requirements. An unauthenticated attacker may access affected endpoints to view or modify data when a developer customizes an operation with @MethodProperties without explicitly redeclaring security roles.

mitigation

Review customized generated operations that use @MethodProperties and explicitly declare the required security roles on each affected operation. Until a fixed release is identified, restrict exposure to affected endpoints and enforce authorization outside the generated endpoint where possible.

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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.39%31st percentile
agent run time
31m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-12 18:41Z
Δ 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

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-10-12 18:41Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-87744

this entry in the feed

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

{
  "etk_id": "ETK-2026-1408",
  "cve_id": "CVE-2026-87744",
  "display_id": "CVE-2026-87744",
  "ghsa_id": "GHSA-jh67-c59w-8h9x",
  "euvd_id": "EUVD-2026-97766",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Authentication bypass in Quarkus REST Data Panache",
  "summary": "Quarkus REST Data Panache generated endpoints can lose inherited class-level security requirements. An unauthenticated attacker may access affected endpoints to view or modify data when a developer customizes an operation with @MethodProperties without explicitly redeclaring security roles.",
  "mitigation": "Review customized generated operations that use @MethodProperties and explicitly declare the required security roles on each affected operation. Until a fixed release is identified, restrict exposure to affected endpoints and enforce authorization outside the generated endpoint where possible.",
  "vendor": "Red Hat",
  "product": "Exploit Intelligence",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "exploit-intelligence/agent-client-rhel9",
      "purl": null
    },
    {
      "affected_notes": [],
      "affected_ranges": [],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "quarkus-hibernate-orm-rest-data-panache",
      "purl": null
    }
  ],
  "cwes": [
    425
  ],
  "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.0039,
  "epss_percentile": 0.3131,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 31.116444283333333,
  "t0_at": "2026-10-12T18:41:46.751000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-12T20:03:56.338270+00:00",
      "days": 0.05705540821759259,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T18:41:46.751000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-12T18:41:46.751000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-12T18:41:46.751000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-87744"
    }
  }
}

published 2026-10-12 19:32Z
last change 2026-10-21 05:31Z

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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.