Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐍
🐍 PyPI
Not in CISA KEV
MEDIUM severity

GHSA-mrj3-f2h4-7w45 — saleor

MEDIUMFix: saleor/saleor#15697

GHSA-mrj3-f2h4-7w45 is a medium-severity (CVSS 4.2) CWE-359 vulnerability in saleor. A fix is available for saleor — see the affected versions and patch details below.

Saleor: Customers' addresses leak when using Warehouse as a `Pickup: Local stock only` delivery method

Also known asCVE-2024-29888PYSEC-2026-1890
Published
Mar 28, 2024
Updated
Jul 28, 2026
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Sep 22, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-mrj3-f2h4-7w45.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs44th percentile — riskier than 44% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

GHSA-mrj3-f2h4-7w45 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

Real-World Exposure

6 pkgs affected
🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor🐍saleor

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Using Pickup: Local stock only as a click-and-collect points could cause a leak of customer addresses

Details

When using Pickup: Local stock only click-and-collect as a delivery method in specific conditions the customer could overwrite the warehouse address with its own, which exposes its address as click-and-collect address.

Impact

The vulnerability can cause the leak of customer's address when using click-and-collect delivery option marked as Local stock only. It has impact on all orders with click-and-collect delivery method marked as Pickup:Local stock only The affected versions: >=3.14.56 <3.14.61, >=3.15.31 <3.15.37, >=3.16.27 <3.16.34, >=3.17.25 <3.17.32, >=3.18.19 <3.18.28, >=3.19.5 <3.19.15 This issue has been patched in versions: 3.14.61, 3.15.37, 3.16.34, 3.17.32, 3.18.28, 3.19.15

Workaround

We strongly recommend upgrading to the latest versions, in case of inability to upgrade straight away, possible workarounds are:

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐍PyPIsaleor≥ 3.14.56&&< 3.14.613.14.61pip install --upgrade 'saleor==3.14.61'
🐍PyPIsaleor≥ 3.15.31&&< 3.15.373.15.37pip install --upgrade 'saleor==3.15.37'
🐍PyPIsaleor≥ 3.16.27&&< 3.16.343.16.34pip install --upgrade 'saleor==3.16.34'
🐍PyPIsaleor≥ 3.17.25&&< 3.17.323.17.32pip install --upgrade 'saleor==3.17.32'
🐍PyPIsaleor≥ 3.18.19&&< 3.18.283.18.28pip install --upgrade 'saleor==3.18.28'
🐍PyPIsaleor≥ 3.19.5&&< 3.19.153.19.15pip install --upgrade 'saleor==3.19.15'

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for saleor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update saleor to 3.14.61 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-mrj3-f2h4-7w45 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-mrj3-f2h4-7w45 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-mrj3-f2h4-7w45. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary Using `Pickup: Local stock only` as a click-and-collect points could cause a leak of customer addresses ### Details When using `Pickup: Local stock only` click-and-collect as a delivery method in specific conditions the customer could overwrite the warehouse address with its own, which exposes its address as click-and-collect address. ### Impact The vulnerability can cause the leak of customer's address when using click-and-collect delivery option marked as `Local stock only`. It has impact on all orders with click-and-collect delivery method marked as `Pickup:Local stock only` T
O3 Security · Impact-Aware SCA

Is GHSA-mrj3-f2h4-7w45 in your dependencies?

O3 Security finds GHSA-mrj3-f2h4-7w45 across PyPI dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works
GHSA-mrj3-f2h4-7w45: saleor (Medium 4.2) | O3 Security