Code execution via unrestricted Java deserialization
Published Oct 24, 2025 · Updated Oct 24, 2025
Insecure deserialization in TAXTELECOM pgCodeKeeper 10.12.0 allows remote attackers to execute code through a crafted .ser file. Utils.deserialize passes the untrusted stream directly to ObjectInputStream.readObject without an input filter or class allowlist. The file must reach a code path that invokes this function, and successful exploitation runs code with the pgCodeKeeper process's privileges.
Summary
What happened
Insecure deserialization in TAXTELECOM pgCodeKeeper 10.12.0 allows remote attackers to execute code through a crafted .ser file. Utils.deserialize passes the untrusted stream directly to ObjectInputStream.readObject without an input filter or class allowlist. The file must reach a code path that invokes this function, and successful exploitation runs code with the pgCodeKeeper process's privileges.
The record
- CVE
- CVE-2025-46183
- Published
- Oct 24, 2025
- Updated
- Oct 24, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 24, 2025CVE publishedPublication date reported by the CVE source.
- Oct 24, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No public exploit references are available in this record.
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