CVE-2026-47065
Proxy Class Deserialization Bypass in Apache Commons
Publication date: 2026-06-03
Last updated on: 2026-06-03
Assigner: Apache Software Foundation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| apache | commons_lang | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability involves the Java deserialization process in the Apache Commons Lang library. Specifically, when deserializing a serialized stream containing a java.lang.reflect.Proxy class, the method ObjectInputStream.resolveProxyClass is called. This method uses Class.forName to load each interface of the proxy class, bypassing the list of accepted classes, which can allow an attacker to bypass security filters.
Additionally, for any class on the allow-list, deserializing a stream that names it triggers the class's static initializer before any instance is constructed. Since many real-world classes have static initializers with side effects, this can be exploited by an attacker who supplies a class name on the allow-list.
Both issues have been fully addressed in the fix.
How can this vulnerability impact me? :
This vulnerability can have severe impacts as indicated by its high CVSS score of 9.8. An attacker can bypass security filters during deserialization, potentially leading to remote code execution or other malicious actions without any privileges or user interaction.
Triggering static initializers of allow-listed classes can cause unintended side effects, which might be exploited to compromise the applicationβs integrity, confidentiality, and availability.
What immediate steps should I take to mitigate this vulnerability?
The vulnerability described as ZDRES-232 and ZDRES-233 in the Apache Commons Lang library has been fully addressed.
To mitigate this vulnerability, ensure that you update to the fixed version of the affected software where these issues have been resolved.
Since the vulnerability involves deserialization bypasses via java.lang.reflect.Proxy and static initializers triggered during deserialization, applying the official patches or upgrading to a version that includes these fixes is the immediate recommended step.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.