CVE-2026-108097: CVE-2026-108097: Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnera…
Unknown · Use · NVD published 2026-10-30 · posted 2026-11-04 · last modified 2026-10-31
CVE-2026-108097 at a glance
CVE-2026-108097 is a vulnerability in Use. NVD published it on 2026-10-30 and classifies the weakness as CWE-470. Public exploit code: 3 public GitHub proof-of-concept repositories from 3 accounts, with the earliest exploit evidence dated 2026-10-30. FIRST EPSS puts the probability of exploitation activity in the next 30 days at 0.33% (percentile 25.7, scored 2026-11-03). NVD does not list a fixed version, so the vendor advisory is the reference for the fix. Its CVERadar threat level is 29/100.
What it is
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') vulnerability in Drupal Drupal core allows Reflection Injection. This issue affects Drupal core versions: from 8.9.0 to 10.6.19, from 11.0.0 to 11.3.19, from 11.4.0 to 11.4.10, from 12.0.0-alpha1 to 12.0.0-beta2.
| Weakness | CWE-470 definition |
|---|---|
| ATT&CK tactics | n/a |
Exploitation evidence
First exploit evidence seen: 2026-10-30 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
3 public repositories from 3 accounts, first seen 2026-10-30. Most starred: fortbridge/cve-2026-108097-research (1 stars), view the fortbridge/cve-2026-108097-research repository on GitHub.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
Patches, mitigations and detection
Fixed versions
NVD does not list a fixed version for this CVE. Use the vendor advisory below.
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
No vendor-tagged reference yet; see the full reference list.
Detection Generic guidance
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.
If you have lost track of what is reachable from the internet, LayerLogix can inventory your exposed services.