How severe is GHSA-qpv2-jxc7-3638?

GHSA-qpv2-jxc7-3638 has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-qpv2-jxc7-3638?

GHSA-qpv2-jxc7-3638 affects the following packages: snipe/snipe-it (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qpv2-jxc7-3638?

Update snipe/snipe-it to 5.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qpv2-jxc7-3638 is resolved across your whole dependency graph.

How do I detect GHSA-qpv2-jxc7-3638 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snipe/snipe-it. 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-qpv2-jxc7-3638 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-qpv2-jxc7-3638?

O3 pinpoints whether GHSA-qpv2-jxc7-3638 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-qpv2-jxc7-3638 actively exploited in the wild?

Yes. There are 1 known exploit references for GHSA-qpv2-jxc7-3638, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for GHSA-qpv2-jxc7-3638?

GHSA-qpv2-jxc7-3638 has an EPSS (Exploit Prediction Scoring System) score of 1.0%, placing it in the 59th 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-qpv2-jxc7-3638?

GHSA-qpv2-jxc7-3638 is classified as CWE-203 (CWE-203). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qpv2-jxc7-3638 published, and has it been updated?

GHSA-qpv2-jxc7-3638 was published on February 15, 2022 and was last updated on February 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-qpv2-jxc7-3638

MEDIUM

Exposure of Sensitive Information in snipe/snipe-it

Also known asCVE-2022-0569

Published

Feb 15, 2022

Updated

Feb 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

1 known

EPSS Exploitation Probability

via FIRST.org ↗

1.0%probability of exploitation in next 30 days

Lower Risk59th percentile+0.67%

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

1 pkg affected

🐘snipe/snipe-it

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

Observable Discrepancy in Packagist snipe/snipe-it prior to v5.3.10.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`snipe/snipe-it`	all versions	5.3.10

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Observable Discrepancy in Packagist snipe/snipe-it prior to v5.3.9.

huntr.devNVDFeb 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for snipe/snipe-it. 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 snipe/snipe-it to 5.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qpv2-jxc7-3638 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-qpv2-jxc7-3638 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-qpv2-jxc7-3638. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Observable Discrepancy in Packagist snipe/snipe-it prior to v5.3.10.

O3 Security · Impact-Aware SCA

Is GHSA-qpv2-jxc7-3638 in your dependencies?

O3 detects GHSA-qpv2-jxc7-3638 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