Is org.apache.james:james-server 3.8 vulnerable?

Maven · 3 releases from 3.8.0 to 3.8.2 · latest org.apache.james:james-server is 3.9.1 · checked 18 Nov 2026

No known advisories in the last release

org.apache.james:james-server 3.8.2, the last 3.8 release, has no known advisories. 2 advisories affect earlier 3.8.x releases, so update to 3.8.2.

Update within 3.8:mvn versions:use-dep-version -Dincludes=org.apache.james:james-server -DdepVersion=3.8.2 -DforceVersion=true

Is your project on an affected org.apache.james:james-server?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Fixed within 3.8.x, affecting earlier releases

  • HighCVE-2023-51747GHSA-p5q9-86w4-2xr527 Feb 2024

    SMTP smuggling in Apache James

    Affected
    <3.7.5 · >=3.8.0 <3.8.1
    Fixed in
    3.7.5, 3.8.1
  • CriticalCVE-2023-51518GHSA-px7w-c9gw-7gj327 Feb 2024

    Apache James server: Privilege escalation via JMX pre-authentication deserialization

    Affected
    <3.7.5 · >=3.8.0 <3.8.1
    Fixed in
    3.7.5, 3.8.1

Every org.apache.james:james-server 3.8.x release

Affected: 3.8.0. 3.8.1 and later are not affected. Latest org.apache.james:james-server: 3.9.1.

VersionKnown advisories
org.apache.james:james-server 3.8.2None
org.apache.james:james-server 3.8.1None
org.apache.james:james-server 3.8.0CVE-2023-51747, CVE-2023-51518

Which of your client projects are still on org.apache.james:james-server 3.8?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact org.apache.james:james-server version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other org.apache.james:james-server versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the Maven registry. Refreshed daily.