Ant Media Server vulnerable to a local privilege escalation
CVE-2024-32656GHSA-qwhw-hh9j-54f5
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (io.antmedia:ant-media-server 2.9.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven io.antmedia:ant-media-server
- Affected
- >= 2.6.0, < 2.9.0
- Fixed in
- 2.9.0
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-qwhw-hh9j-54f5 lists affected ranges: Maven io.antmedia:ant-media-server >=2.6.0 <2.9.0
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.8 · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- EPSS
- CVE-2024-32656: 0.24% estimated exploitation activity in the next 30 days; percentile 15.67 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Impact We have identified a local privilege escalation vulnerability in Ant Media Server which allows any unprivileged operating system user account to escalate privileges to the root user account on the system. This vulnerability arises from Ant Media Server running with Java Management Extensions (JMX) enabled and authentication disabled on localhost on port 5599/TCP. This vulnerability is nearly identical to the local privilege escalation vulnerability CVE-2023-26269 identified in Apache James. Any unprivileged operating system user can connect to the JMX service running on port 5599/TCP on localhost and leverage the MLet Bean within JMX to load a remote MBean from an attacker-controlled server. This allows an attacker to execute arbitrary code within the Java process run by Ant Media Server and execute code within the context of the “antmedia” service account on the system. Patches 2.9.0 Workarounds Remote the following parameters from antmedia.service file Thank you Adam Crosser…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-qwhw-hh9j-54f5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2024-32656 Advisory: Ant Media Server vulnerable to a local privilege escalation IDs: CVE-2024-32656, GHSA-qwhw-hh9j-54f5 Record: https://patchnext.com/advisories/cve-2024-32656 (revision 1, source checked 26 Oct 2026, 16:30 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.8) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: io.antmedia:ant-media-server 2.9.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven io.antmedia:ant-media-server: affected >= 2.6.0, < 2.9.0; fixed in 2.9.0 ## Suggested inspection (read-only) - Maven io.antmedia:ant-media-server: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on io.antmedia:ant-media-server. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-qwhw-hh9j-54f5 (GitHub-reviewed advisory GHSA-qwhw-hh9j-54f5 lists affected ranges: Maven io.antmedia:ant-media-server >=2.6.0 <2.9.0) Commands are suggestions: review each one before running it.
Loading voting…