CVE-2026-33467: Improper Verification of Cryptographic Signature (CWE-347) in Elastic Package Registry could allow an attacker

Q: How do I fix CVE-2026-33467?

elastic package registry: upgrade to 1.38.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-33467 being exploited?

CVE-2026-33467 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-33467 affect?

CVE-2026-33467 affects elastic package registry. Severity is medium (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

Q: How urgent is CVE-2026-33467?

Priority 26/100. Remotely exploitable, no login, no user action

Routine

MEDIUM 5.9REMOTEUPGRADE

CVE-2026-33467 is a medium-severity flaw (CVSS 5.9) affecting elastic package registry. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	5.9 (Medium)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.1% (top 97%)
CISA exploited list	No
Weakness	CWE-347
Published	2026-04-28
Last modified	2026-07-24

Publisher (CNA): Elastic · Vendor: elastic

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-04-28 22:16 UTCPublished CVE record published
2026-07-24 23:10 UTCUpdated Record last modified

elastic elastic package registry UPGRADE

Affected: < 1.38.0

Fixed in: 1.38.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy elastic-package-registry || rpm -q elastic-package-registry || elastic-package-registry --version

2. UPGRADE to 1.38.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade elastic-package-registry

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade elastic-package-registry

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-33467?

elastic package registry: upgrade to 1.38.0. Exact commands for each OS are on this page.

Is CVE-2026-33467 being exploited?

CVE-2026-33467 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-33467 affect?

CVE-2026-33467 affects elastic package registry. Severity is medium (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

How urgent is CVE-2026-33467?

Priority 26/100. Remotely exploitable, no login, no user action

References

← Back to latest CVEs