CVE-2026-113874

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

GHSA-qw7x-rp32-35vw ↗EUVD-2026-108274 ↗

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.
SmileCDR HAPI FHIR < *
fixed in *
ETK-2026-2487Zero's internal tracking ID, independent of the CVE number., permanent identifier
29msince last run
22mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+1h39m
0
+4h
+6h
+8h
+10h
+12h

description

SmileCDR HAPI FHIR can fail to preserve tenant partition isolation when processing bundle requests. An authenticated user permitted in one tenant may access or modify data belonging to another tenant if partition entitlement enforcement is not enabled.

mitigation

Enable and enforce storage-partition entitlement checks. Configure the service so request bundle data cannot override partition identity established by trusted routing or authentication sources.

fixed in *

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
22m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 17:58Z
Δ 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-22 17:58Z
    ghsa: trigger signal, started the run
  2. 2026-10-22 17:58Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2487",
  "cve_id": "CVE-2026-113874",
  "display_id": "CVE-2026-113874",
  "ghsa_id": "GHSA-qw7x-rp32-35vw",
  "euvd_id": "EUVD-2026-108274",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Cross-tenant authorization bypass in SmileCDR HAPI FHIR",
  "summary": "SmileCDR HAPI FHIR can fail to preserve tenant partition isolation when processing bundle requests. An authenticated user permitted in one tenant may access or modify data belonging to another tenant if partition entitlement enforcement is not enabled.",
  "mitigation": "Enable and enforce storage-partition entitlement checks. Configure the service so request bundle data cannot override partition identity established by trusted routing or authentication sources.",
  "vendor": "SmileCDR",
  "product": "HAPI FHIR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < *"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "*"
      ],
      "package_name": "HAPI FHIR",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 22.1375118,
  "t0_at": "2026-10-22T17:58:56.709000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-22T17:58:56.709000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T17:58:56.709000+00:00",
      "url": "https://github.com/advisories/GHSA-qw7x-rp32-35vw"
    }
  }
}

published 2026-10-22 19:16Z
last change 2026-10-22 20:01Z

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.