Package integrity bypass via unsigned package acceptance
Published Apr 28, 2026 · Updated Apr 28, 2026
Improper signature verification in Elastic Package Registry 1.37.0 and earlier allows attackers to substitute packages via intercepted traffic. The local indexer silently accepted packages with no signature path, while proxy mode permitted an HTTP upstream without an explicit insecure override. Only self-hosted deployments that synchronize from an upstream source are affected; Elastic's public registry and deployments that pull directly from it are unaffected.
Summary
What happened
Improper signature verification in Elastic Package Registry 1.37.0 and earlier allows attackers to substitute packages via intercepted traffic. The local indexer silently accepted packages with no signature path, while proxy mode permitted an HTTP upstream without an explicit insecure override. Only self-hosted deployments that synchronize from an upstream source are affected; Elastic's public registry and deployments that pull directly from it are unaffected.
The record
- CVE
- CVE-2026-33467
- Published
- Apr 28, 2026
- Updated
- Apr 28, 2026
- Vendor
- Elastic
- Product
- Elastic Package Registry
- Classifications
- CWE-347, T1195.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 28, 2026CVE publishedPublication date reported by the CVE source.
- Apr 28, 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=0.1.0 <=1.37.0
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
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