How severe is GHSA-v84g-cf5j-xjqx?

No CVSS score has been assigned to GHSA-v84g-cf5j-xjqx yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-v84g-cf5j-xjqx?

GHSA-v84g-cf5j-xjqx affects the following packages: org.apache.james:james-server (Maven). Ecosystems affected: Maven.

How do I fix GHSA-v84g-cf5j-xjqx?

Update org.apache.james:james-server to 3.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v84g-cf5j-xjqx is resolved across your whole dependency graph.

How do I detect GHSA-v84g-cf5j-xjqx in my Maven dependencies?

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

How do I mitigate GHSA-v84g-cf5j-xjqx if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

How does O3 Security protect against GHSA-v84g-cf5j-xjqx?

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

Is GHSA-v84g-cf5j-xjqx actively exploited in the wild?

No public exploit code has been indexed for GHSA-v84g-cf5j-xjqx 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-v84g-cf5j-xjqx?

GHSA-v84g-cf5j-xjqx has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 77th 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.

When was GHSA-v84g-cf5j-xjqx published, and has it been updated?

GHSA-v84g-cf5j-xjqx was published on February 8, 2022 and was last updated on December 5, 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-v84g-cf5j-xjqx: james-server

EPSS Exploitation Probability

via FIRST.org ↗

1.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs77th percentile — riskier than 77% 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.

Real-World Exposure

1 pkg affected

☕org.apache.james:james-server

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

Description

Apache James Server prior to version 3.6.2 contains a path traversal vulnerability. The fix for CVE-2021-40525 does not prepend delimiters upon valid directory validations. Affected implementations include: - maildir mailbox store - Sieve file repository This enables a user to access other users data stores (limited to user names being prefixed by the value of the username being used).

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.james:james-server`	all versions	3.6.2`org.apache.james:james-server:3.6.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.james:james-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.james:james-server to 3.6.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v84g-cf5j-xjqx is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v84g-cf5j-xjqx can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

Apache James Server prior to version 3.6.2 contains a path traversal vulnerability. The fix for CVE-2021-40525 does not prepend delimiters upon valid directory validations. Affected implementations include: - maildir mailbox store - Sieve file repository This enables a user to access other users data stores (limited to user names being prefixed by the value of the username being used).

O3 Security · Impact-Aware SCA

Is GHSA-v84g-cf5j-xjqx in your dependencies?

O3 Security finds GHSA-v84g-cf5j-xjqx across Maven 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-v84g-cf5j-xjqx — james-server