Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.2

Sylius has a Promotion Usage Limit Bypass via Race Condition

CVE-2026-31824GHSA-7mp4-25j8-hp5q

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (sylius/sylius 2.2.3, 2.1.12, 2.0.16, 1.14.18, 1.13.15, 1.12.23, 1.11.17, 1.10.16, 1.9.12), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist sylius/sylius

    Affected
    <= 1.9.11>= 1.10.0, <= 1.10.15>= 1.11.0, <= 1.11.16>= 1.12.0, <= 1.12.22>= 1.13.0, <= 1.13.14>= 1.14.0, <= 1.14.17>= 2.0.0, <= 2.0.15>= 2.1.0, <= 2.1.11>= 2.2.0, <= 2.2.2
    Fixed in
    1.10.16, 2.1.12, 1.11.17, 1.14.18, 1.12.23, 2.0.16, 1.13.15, 2.2.3, 1.9.12

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-7mp4-25j8-hp5q lists affected ranges: Packagist sylius/sylius >=0 =1.10.0 =1.11.0 =1.12.0 =1.13.0 =1.14.0 =2.0.0 =2.1.0 =2.2.0 <=2.2.2

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.2 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L
EPSS
  • CVE-2026-31824: 0.19% estimated exploitation activity in the next 30 days; percentile 8.72 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Impact A Time-of-Check To Time-of-Use (TOCTOU) race condition was discovered in the promotion usage limit enforcement. The same class of vulnerability affects three independent limits: 1. Promotion usage limit - the global used counter on Promotion entities 2. Coupon usage limit - the global used counter on PromotionCoupon entities 3. Coupon per-customer usage limit - the per-customer redemption count on PromotionCoupon entities In all three cases, the eligibility check reads the used counter (or order count) from an in-memory Doctrine entity during validation, while the actual usage increment in OrderPromotionsUsageModifier happens later during order completion — with no database-level locking or atomic operations between the two phases. Because Doctrine flushes an absolute value (SET used = 1) rather than an atomic increment (SET used = used + 1), and because the affected entities lack optimistic locking, concurrent requests all read the same stale usage counts and pass the…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-7mp4-25j8-hp5q

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31824

Advisory: Sylius has a Promotion Usage Limit Bypass via Race Condition
IDs: CVE-2026-31824, GHSA-7mp4-25j8-hp5q
Record: https://patchnext.com/advisories/cve-2026-31824 (revision 1, source checked 26 Oct 2026, 14:38 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sylius/sylius 2.2.3, 2.1.12, 2.0.16, 1.14.18, 1.13.15, 1.12.23, 1.11.17, 1.10.16, 1.9.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist sylius/sylius: affected <= 1.9.11; >= 1.10.0, <= 1.10.15; >= 1.11.0, <= 1.11.16; >= 1.12.0, <= 1.12.22; >= 1.13.0, <= 1.13.14; >= 1.14.0, <= 1.14.17; >= 2.0.0, <= 2.0.15; >= 2.1.0, <= 2.1.11; >= 2.2.0, <= 2.2.2; fixed in 1.10.16, 2.1.12, 1.11.17, 1.14.18, 1.12.23, 2.0.16, 1.13.15, 2.2.3, 1.9.12

## Suggested inspection (read-only)
- Packagist sylius/sylius: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sylius/sylius.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-7mp4-25j8-hp5q (GitHub-reviewed advisory GHSA-7mp4-25j8-hp5q lists affected ranges: Packagist sylius/sylius >=0 =1.10.0 =1.11.0 =1.12.0 =1.13.0 =1.14.0 =2.0.0 =2.1.0 =2.2.0 <=2.2.2)

Commands are suggestions: review each one before running it.

Loading voting…