CVE-2026-85520

validatedZero produced an exploit or a check.

GHSA-mxmh-vx83-qfxg ↗EUVD-2026-88735 ↗

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).+2h22mkevAttacks confirmed in the real world.0d
MyPresta Google Merchant Center Feed >= 1.9.1, <= 2.3.8
fixed in 2.3.9
CWE-73 External Control of File Name or Path
ETK-2026-515, permanent identifier
+4.6dTTV
42mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal +0dcve.org publication+0.5dpublic poc+0.6dkev+1.0dcheck available+5.0dagent stopped
0
+2d
+3d
+4d

description

The Google Merchant Center Feed (gmfeed) module for PrestaShop has an unauthenticated file-write vulnerability in its feed endpoint. An unauthenticated remote attacker may write attacker-controlled files and achieve code execution if the vulnerable endpoint is reachable.

mitigation

Upgrade the Google Merchant Center Feed (gmfeed) module to version 2.3.9 or later. Restrict public access to the module's feed endpoint until the update is applied.

fixed in 2.3.9

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.
0.99%62nd percentile
agent run time
42m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-09-29 11:28Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
+2h22m
Δ to kevAttacks confirmed in the real world.
0d

outcome

Mechanism verified: the exploit fired on the vulnerable build and stayed silent on the patched one, but the server it ran against was ours, so no check ships for it.

source signals

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

  1. 2026-09-29
    vulncheck_kev: trigger signal, started the run
  2. 2026-09-29 00:00Z
  3. 2026-09-29 11:28Z
  4. 2026-10-04 04:20Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-515",
  "cve_id": "CVE-2026-85520",
  "display_id": "CVE-2026-85520",
  "ghsa_id": "GHSA-mxmh-vx83-qfxg",
  "euvd_id": "EUVD-2026-88735",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated arbitrary file write in PrestaShop gmfeed",
  "summary": "The Google Merchant Center Feed (gmfeed) module for PrestaShop has an unauthenticated file-write vulnerability in its feed endpoint. An unauthenticated remote attacker may write attacker-controlled files and achieve code execution if the vulnerable endpoint is reachable.",
  "mitigation": "Upgrade the Google Merchant Center Feed (gmfeed) module to version 2.3.9 or later. Restrict public access to the module's feed endpoint until the update is applied.",
  "vendor": "MyPresta",
  "product": "Google Merchant Center Feed",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.9.1, <= 2.3.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.3.9"
      ],
      "package_name": "Google Merchant Center Feed",
      "purl": null
    }
  ],
  "cwes": [
    73
  ],
  "cvss_score": 9.3,
  "cvss_src": "nvd",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
  "epss_score": 0.0099,
  "epss_percentile": 0.6214,
  "epss_asof": "2026-10-21",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "mechanism_verified",
  "exploit": false,
  "pipeline_minutes": 41.698772016666666,
  "t0_at": "2026-09-29T11:28:55.953000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-04T00:54:52.798072+00:00",
      "days": 4.559685706851852,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T11:28:55.953000+00:00",
      "url": null
    },
    "kev": {
      "at": "2026-09-29T00:00:00+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T11:28:55.953000+00:00",
      "precision": "day",
      "url": "https://vulncheck.com/cve/CVE-2026-85520"
    },
    "public_poc": {
      "at": "2026-09-29T13:51:05+00:00",
      "days": 0.09871582175925926,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T11:28:55.953000+00:00",
      "url": "https://github.com/murrez/CVE-2026-85520"
    },
    "trigger_signal": {
      "at": "2026-09-29T00:00:00+00:00",
      "days": -0.47842538194444445,
      "is_lower_bound": false,
      "measured_at": "2026-09-29T11:28:55.953000+00:00",
      "url": "https://vulncheck.com/cve/CVE-2026-85520"
    }
  }
}

published 2026-10-04 00:13Z
last change 2026-10-21 20:26Z

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.