CVE-2026-111901

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

GHSA-45x8-rjq5-9jpp ↗EUVD-2026-103319 ↗

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.
thorsten phpMyFAQ >= 4.2.0-alpha, < 4.2.0-beta
fixed in 4.2.0-beta
ETK-2026-1914Zero's internal tracking ID, independent of the CVE number., permanent identifier
2d 04h 01msince last run
45mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+30h03m
0
+2h
+4h
+6h
+8h
+10h

description

phpMyFAQ releases from 4.2.0-alpha through versions before 4.2.0-beta are affected in the public FAQ and search API endpoints. An unauthenticated remote attacker can make concurrent requests that consume excessive CPU and memory, potentially interrupting service.

mitigation

Upgrade phpMyFAQ to 4.2.0-beta or later. Until upgrade, rate-limit and restrict public access to the FAQ and search API endpoints at the proxy or network boundary.

fixed in 4.2.0-beta

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.34%26th percentile
agent run time
45m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-17 18:46Z
Δ 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-17 18:46Z
    ghsa: trigger signal, started the run
  2. 2026-10-17 18:46Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-1914",
  "cve_id": "CVE-2026-111901",
  "display_id": "CVE-2026-111901",
  "ghsa_id": "GHSA-45x8-rjq5-9jpp",
  "euvd_id": "EUVD-2026-103319",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated resource exhaustion in phpMyFAQ API endpoints",
  "summary": "phpMyFAQ releases from 4.2.0-alpha through versions before 4.2.0-beta are affected in the public FAQ and search API endpoints. An unauthenticated remote attacker can make concurrent requests that consume excessive CPU and memory, potentially interrupting service.",
  "mitigation": "Upgrade phpMyFAQ to 4.2.0-beta or later. Until upgrade, rate-limit and restrict public access to the FAQ and search API endpoints at the proxy or network boundary.",
  "vendor": "thorsten",
  "product": "phpMyFAQ",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 4.2.0-alpha, < 4.2.0-beta"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "4.2.0-beta"
      ],
      "package_name": "phpMyFAQ",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
  "epss_score": 0.0034,
  "epss_percentile": 0.2642,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 44.80130028333333,
  "t0_at": "2026-10-17T18:46:22.075000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-17T18:46:22.075000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-17T18:46:22.075000+00:00",
      "url": "https://github.com/advisories/GHSA-45x8-rjq5-9jpp"
    }
  }
}

published 2026-10-17 23:06Z
last change 2026-10-21 01:20Z

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.