Credential disclosure via Base64-encoded HTTP headers
Published Jan 7, 2026 · Updated Jan 7, 2026
Weak credential encoding in Efacec QC 60/90/120 version 8 allows attackers to obtain web server credentials by intercepting login requests. The device places the username and password in Base64 form in HTTP authorization headers, providing encoding rather than transport confidentiality. Exploitation requires adjacent-network access and low privileges; the published impact is credential disclosure without integrity or availability effects.
Summary
What happened
Weak credential encoding in Efacec QC 60/90/120 version 8 allows attackers to obtain web server credentials by intercepting login requests. The device places the username and password in Base64 form in HTTP authorization headers, providing encoding rather than transport confidentiality. Exploitation requires adjacent-network access and low privileges; the published impact is credential disclosure without integrity or availability effects.
The record
- CVE
- CVE-2026-22543
- Published
- Jan 7, 2026
- Updated
- Jan 7, 2026
- Vendor
- Efacec
- Product
- QC 60/90/120
- Classifications
- CWE-261, T1040
- Attack vector
- adjacent
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 7, 2026CVE publishedPublication date reported by the CVE source.
- Jan 7, 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=8
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.
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