Service interruption via unchecked bit-length processing
Published Dec 1, 2025 · Updated Dec 1, 2025
Improper input validation in Tempus Ex hello-video-codec 0.1.0 allows attackers to interrupt service via a crafted bit-length argument. BitstreamWriter::write_bits() accepts an unchecked length and repeatedly emits padding bits in proportion to that value. A user must cause an application using the library to process the crafted input; the reported impact is limited to availability.
Summary
What happened
Improper input validation in Tempus Ex hello-video-codec 0.1.0 allows attackers to interrupt service via a crafted bit-length argument. BitstreamWriter::write_bits() accepts an unchecked length and repeatedly emits padding bits in proportion to that value. A user must cause an application using the library to process the crafted input; the reported impact is limited to availability.
The record
- CVE
- CVE-2025-63095
- Published
- Dec 1, 2025
- Updated
- Dec 1, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 1, 2025CVE publishedPublication date reported by the CVE source.
- Dec 1, 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
- CVE-2025-63095 proof of conceptproof of concept · unverified
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