Unauthenticated code execution via hostile JMX deserialization
Published Jun 6, 2025 · Updated Jun 9, 2025
Unsafe deserialization in Kafka UI 1.0.0 allows remote attackers to execute arbitrary code through a configured JMX metrics endpoint. The unauthenticated /api/config route accepts an attacker-controlled cluster, and the metrics client follows its JMX RMI URL and deserializes objects returned by the hostile JRMP server. Dynamic configuration must be enabled and the server must reach the hostile JMX endpoint; successful commands run as the application service account.
Summary
What happened
Unsafe deserialization in Kafka UI 1.0.0 allows remote attackers to execute arbitrary code through a configured JMX metrics endpoint. The unauthenticated /api/config route accepts an attacker-controlled cluster, and the metrics client follows its JMX RMI URL and deserializes objects returned by the hostile JRMP server. Dynamic configuration must be enabled and the server must reach the hostile JMX endpoint; successful commands run as the application service account.
The record
- CVE
- CVE-2025-49127
- Published
- Jun 6, 2025
- Updated
- Jun 9, 2025
- Vendor
- Provectus
- Product
- Kafka UI
- Classifications
- CWE-502, CAPEC-586, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 6, 2025CVE publishedPublication date reported by the CVE source.
- Jun 9, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion== 1.0.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- JMX JRMP deserialization proof of conceptfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo