CVE-2026-111862

validatedZero produced an exploit or a check.

GHSA-6qfj-hq55-w68p ↗EUVD-2026-104460 ↗

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.
RankMath Rank Math SEO PRO 3.0.123
CWE-506 Embedded Malicious Code
ETK-2026-2069Zero's internal tracking ID, independent of the CVE number., permanent identifier
+1.1dTTV
<1mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+26h25magent stopped
0
+6h
+12h
+18h
+24h

description

Some Rank Math SEO PRO 3.0.123 packages obtained between October 15 and 16, 2026 contained malicious code. When one of those packages was activated, an attacker could retain access to the WordPress site and obtain credentials or other secrets accessible to the server; installations outside that download window are not identified as affected.

mitigation

Replace the plugin with Rank Math SEO PRO 3.0.124 and investigate any site that activated a package obtained during the affected window as compromised. Rotate WordPress, database, API, and other server-accessible credentials, and remove unauthorized persistence identified during the investigation.

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.
deterministic
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.72%52nd percentile
agent run time
<1m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-19 16:35Z
Δ 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

Upstream: a detection for this already ships elsewhere, so we didn't generate a new one. The credit goes to whoever did.

source signals

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

  1. 2026-10-19 16:35Z
    cve_org: trigger signal, started the run
  2. 2026-10-20 19:01Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2069",
  "cve_id": "CVE-2026-111862",
  "display_id": "CVE-2026-111862",
  "ghsa_id": "GHSA-6qfj-hq55-w68p",
  "euvd_id": "EUVD-2026-104460",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Supply-chain malware in Rank Math SEO PRO",
  "summary": "Some Rank Math SEO PRO 3.0.123 packages obtained between October 15 and 16, 2026 contained malicious code. When one of those packages was activated, an attacker could retain access to the WordPress site and obtain credentials or other secrets accessible to the server; installations outside that download window are not identified as affected.",
  "mitigation": "Replace the plugin with Rank Math SEO PRO 3.0.124 and investigate any site that activated a package obtained during the affected window as compromised. Rotate WordPress, database, API, and other server-accessible credentials, and remove unauthorized persistence identified during the investigation.",
  "vendor": "RankMath",
  "product": "Rank Math SEO PRO",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "3.0.123"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Rank Math SEO PRO",
      "purl": null
    }
  ],
  "cwes": [
    506
  ],
  "cvss_score": 9.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
  "epss_score": 0.0072,
  "epss_percentile": 0.5294,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "upstream",
  "exploit": false,
  "pipeline_minutes": 0.010014966666666666,
  "t0_at": "2026-10-19T16:35:59.949000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-20T19:01:11.587503+00:00",
      "days": 1.1008291493402778,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T16:35:59.949000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-19T16:35:59.949000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-19T16:35:59.949000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-111862"
    }
  }
}

published 2026-10-19 17:19Z
last change 2026-10-21 07:48Z

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.