Apache James vulnerabilities and CVEs

Known vulnerabilities affecting Apache James, with exploit availability attached to each one, so you can tell a flaw someone has written code for from one nobody has.

6 vulnerabilities tracked.

8.7 Allocation of Resources Without Limits or Throttling in Apache James Mime4J library prior version 0.8.15 allows Denial of Service upon… CVE-2026-85111 6 Nov 2026
— In Apache James server prior version 3.9.1 relying on the SieveFileRepository incorect validation of file paths can result in path… CVE-2026-76168 6 Nov 2026
— Some docker-compose shipped by the project exposes by default Webadmin REST API publically without proper authentication setup. CVE-2026-74756 6 Nov 2026
— In Apache James server prior version 3.9.1 improper validation in JMAP webPush SSRF validation did lead to the possibility to reach… CVE-2026-76171 6 Nov 2026
— In Apache James server prior version 3.9.1 improper Access Control List processing is exposed by the JMAP protocol which do not account for… CVE-2026-49939 6 Nov 2026
— Apache James SASL OAuthBearer/XOAUTH2 prior versions 3.9.1 fails to validate correctly AUD claim of JWT payloads when introspection is not… CVE-2025-66621 6 Nov 2026

What this covers

This feed accumulates forward from the day it started storing records, and a name search that finds nothing here is also looked up against the registers directly — so an older advisory resolves even when it predates the corpus. It is still a reading view, not a substitute for the vendor's own advisory, and absence from this page is not a statement that Apache James is free of vulnerabilities.

Query this from an agent over MCP · Check a lockfile by version

Other products tracked here