CVE-2026-113873

validatedZero produced an exploit or a check.

GHSA-36fr-h72x-63ph ↗

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.
SmileCDR HAPI FHIR < *
fixed in *
CWE-409 Improper Handling of Highly Compressed Data (Data Amplification)
ETK-2026-2477Zero's internal tracking ID, independent of the CVE number., permanent identifier
+32mTTV
21mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+32magent stopped
0
+10min
+20min
+30min

description

SmileCDR HAPI FHIR improperly processes highly compressed input. An unauthenticated attacker able to submit compressed payloads can cause excessive heap consumption or crash certain services when the input is decompressed.

mitigation

Update HAPI FHIR to version *. Restrict untrusted access to endpoints that accept compressed payloads until the update is deployed.

fixed in *

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.
–
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-22 17:57Z
Δ 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 check: a technique exists and was validated, 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:57Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2477",
  "cve_id": "CVE-2026-113873",
  "display_id": "CVE-2026-113873",
  "ghsa_id": "GHSA-36fr-h72x-63ph",
  "euvd_id": null,
  "status": "published",
  "anchor_state": "anchored",
  "title": "Improper compressed-data handling in SmileCDR HAPI FHIR",
  "summary": "SmileCDR HAPI FHIR improperly processes highly compressed input. An unauthenticated attacker able to submit compressed payloads can cause excessive heap consumption or crash certain services when the input is decompressed.",
  "mitigation": "Update HAPI FHIR to version *. Restrict untrusted access to endpoints that accept compressed payloads until the update is deployed.",
  "vendor": "SmileCDR",
  "product": "HAPI FHIR",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < *"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "*"
      ],
      "package_name": "HAPI FHIR",
      "purl": null
    }
  ],
  "cwes": [
    409
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 20.597021233333333,
  "t0_at": "2026-10-22T17:57:52.475000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-22T18:29:57.155415+00:00",
      "days": 0.02227639369212963,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T17:57:52.475000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-22T17:57:52.475000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-22T17:57:52.475000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-113873"
    }
  }
}

published 2026-10-22 18:09Z
last change 2026-10-22 19: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.