Assessment
Why it matters
EPSS is 0.1%; technical severity is CVSS 5.9.
Improper Verification of Cryptographic Signature (CWE-347) in Elastic Package Registry could allow an attacker positioned to intercept network traffic, or to otherwise influence the contents served to a self-hosted registry, to substitute a tampered package without the integrity check failing closed.
Who should care
- Teams operating Elastic Package Registry
- Vulnerability and exposure management teams
- Security operations teams monitoring exploitation activity
Response plan
What I would do
- Confirm whether Elastic Package Registry is present in the environment.
- Identify affected versions and establish whether vulnerable services are exposed or reachable.
- Vendor advisory from discuss.elastic.co
- Review relevant security telemetry for evidence of attempted or successful exploitation.
- Document the remediation decision and track it to verified completion.
Treatment intelligence
Remediation intelligence
Vendor sources are listed before government and third-party guidance. Confirm product applicability and change prerequisites before deployment.
Verification noteAutomated link verification has not completed for this guidance yet.
Technical details
- CVSS vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- CWE
- CWE-347
- Affected versions
- Elastic Elastic Package Registry (End Excluding 1.38.0)
- Fixed versions
- Elastic Elastic Package Registry (Fixed from 1.38.0)
- Published
- 28 April 2026
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
Signal timeline
- CVE published
- Latest EPSS score: 0.1%
- Signal calculated at 10