CVE-2026-82211

validatedZero produced an exploit or a check.

GHSA-65w5-qcwh-f3g3 ↗EUVD-2026-94195 ↗

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.
Nexi XPay Build >= 7.0.0, <= 7.6.2
ETK-2026-853, permanent identifier
+1h27mTTV
37mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+87magent stopped
0
+30min
+60min

description

Nexi XPay Build versions through 7.6.2 inadequately validate payment outcomes submitted to certain public routes. An unauthenticated attacker able to reach those routes may alter or cancel orders and obtain order keys that can reveal guest buyer details.

mitigation

Disable the plugin or restrict unauthenticated access to its payment-result routes until a vendor update is available. Monitor affected orders for unexpected status changes and cancellations.

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.19%7th percentile
agent run time
37m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 06:47Z
Δ 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-07 06:47Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-853",
  "cve_id": "CVE-2026-82211",
  "display_id": "CVE-2026-82211",
  "ghsa_id": "GHSA-65w5-qcwh-f3g3",
  "euvd_id": "EUVD-2026-94195",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment-result validation flaw in Nexi XPay Build",
  "summary": "Nexi XPay Build versions through 7.6.2 inadequately validate payment outcomes submitted to certain public routes. An unauthenticated attacker able to reach those routes may alter or cancel orders and obtain order keys that can reveal guest buyer details.",
  "mitigation": "Disable the plugin or restrict unauthenticated access to its payment-result routes until a vendor update is available. Monitor affected orders for unexpected status changes and cancellations.",
  "vendor": null,
  "product": "Nexi XPay Build",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 7.0.0, <= 7.6.2"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Nexi XPay Build",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N",
  "epss_score": 0.0019,
  "epss_percentile": 0.0783,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 37.19437955,
  "t0_at": "2026-10-07T06:47:53.228000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-07T08:15:20.281584+00:00",
      "days": 0.060729786851851854,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T06:47:53.228000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-07T06:47:53.228000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T06:47:53.228000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-82211"
    }
  }
}

published 2026-10-07 07:39Z
last change 2026-10-21 16:15Z

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.