How severe is GHSA-xjm6-jfmg-qc6p?

GHSA-xjm6-jfmg-qc6p has a CVSS score of 5.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-xjm6-jfmg-qc6p?

GHSA-xjm6-jfmg-qc6p affects the following packages: aimeos/aimeos-core (Packagist), aimeos/aimeos-core (Packagist), aimeos/aimeos-core (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-xjm6-jfmg-qc6p?

Update aimeos/aimeos-core to 2024.04.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjm6-jfmg-qc6p is resolved across your whole dependency graph.

How do I detect GHSA-xjm6-jfmg-qc6p in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/aimeos-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-xjm6-jfmg-qc6p if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against GHSA-xjm6-jfmg-qc6p?

O3 pinpoints whether GHSA-xjm6-jfmg-qc6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-xjm6-jfmg-qc6p actively exploited in the wild?

No public exploit code has been indexed for GHSA-xjm6-jfmg-qc6p yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-xjm6-jfmg-qc6p?

GHSA-xjm6-jfmg-qc6p has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-xjm6-jfmg-qc6p?

GHSA-xjm6-jfmg-qc6p is classified as CWE-270 (CWE-270). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-xjm6-jfmg-qc6p published, and has it been updated?

GHSA-xjm6-jfmg-qc6p was published on May 29, 2024 and was last updated on June 11, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-xjm6-jfmg-qc6p: aimeos/aimeos-core Denial of Service (Medi…

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk35th percentile+0.35%

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.

Blast Radius

3 pkgs affected

🐘aimeos/aimeos-core🐘aimeos/aimeos-core🐘aimeos/aimeos-core

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

Description

Impact

All SaaS and marketplace setups using Aimeos version from 2022/2023/2024 are affected by a potential denial of service attack

Patches

Upgrade to the latest 2022.10 LTS, 2023.10 LTS and 2024.04.7 version of the aimeos/aimeos-core package

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`aimeos/aimeos-core`	≥ 2024.04.1&&< 2024.04.7	2024.04.7
🐘Packagist	`aimeos/aimeos-core`	≥ 2023.04.1&&< 2023.10.17	2023.10.17
🐘Packagist	`aimeos/aimeos-core`	≥ 2022.04.1&&< 2022.10.17	2022.10.17

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/aimeos-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update aimeos/aimeos-core to 2024.04.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-xjm6-jfmg-qc6p is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether GHSA-xjm6-jfmg-qc6p is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-xjm6-jfmg-qc6p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact All SaaS and marketplace setups using Aimeos version from 2022/2023/2024 are affected by a potential denial of service attack ### Patches Upgrade to the latest 2022.10 LTS, 2023.10 LTS and 2024.04.7 version of the aimeos/aimeos-core package

O3 Security · Impact-Aware SCA

Is GHSA-xjm6-jfmg-qc6p in your dependencies?

O3 detects GHSA-xjm6-jfmg-qc6p across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-xjm6-jfmg-qc6p