Information disclosure via Java RMI deserialization
Published Sep 11, 2025 · Updated Sep 11, 2025
Deserialization in SEAT Queue Ticket Kiosk 20250827 and earlier allows remote attackers to read data via Java RMI on an adjacent network. SEAT has not published which registry operation accepts the untrusted serialized object or how input validation fails. Reachability is unauthenticated but limited to the local network, and the published impact is confidentiality loss only.
Summary
What happened
Deserialization in SEAT Queue Ticket Kiosk 20250827 and earlier allows remote attackers to read data via Java RMI on an adjacent network. SEAT has not published which registry operation accepts the untrusted serialized object or how input validation fails. Reachability is unauthenticated but limited to the local network, and the published impact is confidentiality loss only.
The record
- CVE
- CVE-2025-10252
- Published
- Sep 11, 2025
- Updated
- Sep 11, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, CWE-502
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 11, 2025CVE publishedPublication date reported by the CVE source.
- Sep 11, 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.
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.
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