Unauthenticated service interruption via version array injection
Published Feb 9, 2026 · Updated Feb 9, 2026
Improper input validation in Adminer 4.6.2 through 5.4.1 allows remote attackers to persistently interrupt the web service. The unauthenticated ?script=version handler serializes a version[] value as an array, which later reaches openssl_verify() where a string is required and triggers a TypeError. Any network-reachable instance is exposed, and the poisoned shared adminer.version file makes subsequent page loads return HTTP 500 for all users.
Summary
What happened
Improper input validation in Adminer 4.6.2 through 5.4.1 allows remote attackers to persistently interrupt the web service. The unauthenticated ?script=version handler serializes a version[] value as an array, which later reaches openssl_verify() where a string is required and triggers a TypeError. Any network-reachable instance is exposed, and the poisoned shared adminer.version file makes subsequent page loads return HTTP 500 for all users.
The record
- CVE
- CVE-2026-25892
- Published
- Feb 9, 2026
- Updated
- Feb 9, 2026
- Vendor
- Adminer
- Product
- Adminer
- Classifications
- CWE-20, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 9, 2026CVE publishedPublication date reported by the CVE source.
- Feb 9, 2026Record 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=>= 4.6.2, < 5.4.2
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
- Vendor advisory HTTP 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