Cyber Resilience

CVE-2026-105850

Published
06 October 2026
Modified
06 October 2026
CVSS Score v4 8.8
Click a component to see what it means
Raw vectorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/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.0031 22th percentile
Risk Priority 44 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-105850 is a high-severity Improper Enforcement of a Single, Unique Action (CWE-837) vulnerability. Its CVSS base score is 8.8 (High).

Operationally, ranked at the 22th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Payload is a free and open source headless content management system. In @payloadcms/plugin-ecommerce versions before 3.90.0 and canary versions before 4.0.0-canary.34, use of the Stripe payment adapter can allow a Stripe order confirmation to be processed more than once under…

more

certain conditions. This issue is fixed in versions 3.90.0 and 4.0.0-canary.34.

CWE(s)
CWE-837

Related Threats

CVEs Like This One

CVE-2023-6759Shared CWE-837
CVE-2023-6467Shared CWE-837
CVE-2025-62782Shared CWE-837
CVE-2026-44601Shared CWE-837
CVE-2024-4629Shared CWE-837
CVE-2024-11716Shared CWE-837
CVE-2025-62783Shared CWE-837
CVE-2025-62784Shared CWE-837
CVE-2023-6438Shared CWE-837
CVE-2025-54315Shared CWE-837

Affected Assets

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V6.3.3
  • V6.5.1

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement partial match

AC-3 enforces approved authorizations for actions; when policy requires an action to occur only once, proper enforcement directly stops duplicate execution.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 partial match
blocks

Authorization policy enforcement can include rules that restrict actions to a single use.

PR.IR-01 partial match
blocks

Logical access controls can incorporate mechanisms that block replay or repeated actions.

PR.PS-05 partial match
blocks

Preventing execution of unauthorized or duplicate actions directly addresses single-use enforcement.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.5.15 Access control partial match
degrades

Access-control rules can enforce single-use or uniqueness constraints, but the control is broader than this specific weakness.

A.5.18 Access rights partial match
degrades

Managing access rights can include rules that limit an action to one occurrence, yet the control addresses rights in general.

A.5.21 Managing information security in the ICT supply chain partial match
removes
A.8.25 Secure development life cycle partial match
blocks

Secure SDLC practices can require design controls for single-use actions, but the control addresses the entire lifecycle.

A.8.26 Application security requirements partial match
blocks

Application-security requirements can specify single-action enforcement, yet the control is wider in scope.

A.8.28 Secure coding partial match
prevents

Secure-coding standards can mandate checks that prevent repeated actions, but the control covers many coding issues.

References