dbcve.org
Elastic Package RegistryApplication · Elastic

CVE-2026-33467

MEDIUM · 5.9 CVSS v3.1 Published 2026-04-28
Fix available
A fix is available. Upgrade to 1.38.0 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Elastic Package Registry contains a cryptographic signature verification flaw (CWE-347) where integrity checks fail open rather than fail closed. An attacker with network interception capability or who can influence content served to a self-hosted registry can substitute tampered packages without the signature validation rejecting them.

MitigationOrganizations running self-hosted Elastic Package Registries should review network segmentation and ensure attackers cannot intercept or influence registry content. The fix requires Elastic to correct the signature verification logic to properly validate cryptographic signatures and reject tampered packages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Elastic Package RegistryApplication
Affected:< 1.38.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Elastic Package Registry version
    Check the running service version via API endpoint (e.g., curl https://your-registry:8080/api/status or /api/v1/status) or by running 'docker ps' to see the container image tag, or check the binary/service version with 'epr --version' if CLI is available
    Affected if The version shown is below 1.38.0 (e.g., 1.37.0, 1.36.0, etc.)
  2. Confirm the deployment is a self-hosted registry
    Determine if the Elastic Package Registry is self-hosted (on-premises, in your own cloud account, or internal network) rather than using Elastic's hosted service. Check the registry URL configuration in your package deployment pipelines or configuration files
    Affected if The registry URL points to an internal or self-managed endpoint and is not the official Elastic service
  3. Test signature validation behavior
    Attempt to push or deploy a package with an intentionally invalid cryptographic signature to your registry (or a test instance), and observe whether the registry accepts or rejects it. Alternatively, review registry logs for signature validation failures that were still processed
    Affected if Packages with missing, tampered, or invalid signatures are accepted rather than rejected, indicating the fail-open behavior is present
  4. Review registry configuration for signature enforcement
    Examine the Elastic Package Registry configuration file (typically in /etc/epm or the docker/config) for settings related to package signing, such as 'package.signature.required' or 'require-signed-packages'. Also check if any environment variable disables signature verification
    Affected if Signature verification is disabled, not enforced, or set to permissive mode

You are affected if your self-hosted Elastic Package Registry is running a version below 1.38.0 and accepts packages with invalid or unverifiable cryptographic signatures.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.38.0 or later
Fixed in 1.38.0
Interim mitigation

Organizations running self-hosted Elastic Package Registries should review network segmentation and ensure attackers cannot intercept or influence registry content. The fix requires Elastic to correct the signature verification logic to properly validate cryptographic signatures and reject tampered packages.

Recommended fix Moderate confidence

1.38.0

  1. Upgrade Elastic Package Registry to version 1.38.0 or later to resolve the improper signature verification vulnerability.
  2. After upgrading, verify that package integrity checks are functioning correctly by testing package installation from the registry.
  3. Consult Elastic documentation for specific upgrade procedures relevant to your deployment method (Docker, RPM, tarball, etc.).

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Elastic Package Registry Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33467 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data