Vulnerabilities in pkg:golang/github.com/elastic/package-registry

PACKAGE
Advisory Identifier: GHSA-r727-5pf6-47r2
Share
Advisory Summary

CVE-2026-33467 is a MODERATE (CVSS 5.9) elastic package registry has improper vulnerability (CWE-347: Improper Verification of Cryptographic Signature) affecting Github.com/elastic/package registry libraries in the Go ecosystem. The issue involves elastic package registry has improper verification of cryptographic signature. Remediation is available by upgrading affected packages to version 1.38.0.

1 Known Advisory Record(s)
Package Vulnerability Intelligence

pkg:golang/github.com/elastic/package-registry

1 Known Advisory Record(s)

Vulnerability advisories affecting package pkg:golang/github.com/elastic/package-registry. Select an advisory below to view technical details or fixes.

Advisory ID CVE / NVD Severity Summary
GHSA-r727-5pf6-47r2 CVE-2026-33467 MODERATE Elastic Package Registry has Improper Verification of Cryptographic Signature

CVE-2026-33467 at a Glance

CVE Identifier CVE-2026-33467
GHSA Identifier GHSA-r727-5pf6-47r2
Severity MODERATE
CVSS v3.1 Base Score 5.9
CWE Classification CWE-347: Improper Verification of Cryptographic Signature
Affected Product Github.com/elastic/package registry
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.9

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N).

Attack Vector Network (AV:N)
Attack Complexity High (AC:H)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity High (I:H)
Availability None (A:N)

How to Fix CVE-2026-33467

To remediate this vulnerability, upgrade all affected Github.com/elastic/package registry dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/elastic/package-registry fixed: 1.38.0 
Upgrade github.com/elastic/package-registry to 1.38.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

inspect dependencies for github.com/elastic/package-registry

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33467, inspect your project dependencies for Github.com/elastic/package registry:

inspect dependencies for github.com/elastic/package-registry

Analyze the terminal output to locate any version of Github.com/elastic/package registry in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.38.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-347: Improper Verification of Cryptographic Signature, where the product does not verify, or incorrectly verifies, the cryptographic signature for data. In Github.com/elastic/package registry, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

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.

CVE-2026-33467 Affected Github.com/elastic/package registry Versions

1 component(s)
Fixed Versions:
1.38.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/elastic/package-registry
golang/github.com/elastic/package-registry
Go
< 1.38.0
1.38.0

References

NVD — CVE-2026-33467 NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-33467
Github.com/elastic/package registry Security Information SECURITY
https://discuss.elastic.co/t/elastic-package-registry-1-38-0-security-update-esa-2026-27/386081
Github.com/elastic/package registry Source Repository REPOSITORY
https://github.com/elastic/package-registry

Frequently Asked Questions

What is CVE-2026-33467?
CVE-2026-33467 is a security vulnerability in Github.com/elastic/package registry involving Elastic Package Registry has Improper Verification of Cryptographic Signature under CWE-347: Improper Verification of Cryptographic Signature.
Which Github.com/elastic/package registry versions are affected?
Affected versions include releases prior to 1.38.0 across affected packages: github.com/elastic/package-registry.
What version fixes CVE-2026-33467?
Upgrading to 1.38.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/elastic/package-registry affected?
Yes, github.com/elastic/package-registry is affected in releases prior to 1.38.0. Upgrade your dependency to 1.38.0 or later.
What is the CVSS score of CVE-2026-33467?
CVE-2026-33467 has a CVSS v3.1 base score of 5.9 (MODERATE) with vector string CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N.
What CWE is associated with CVE-2026-33467?
CVE-2026-33467 is classified under CWE-347: Improper Verification of Cryptographic Signature (The product does not verify, or incorrectly verifies, the cryptographic signature for data.).
How can I check Go dependencies for CVE-2026-33467?
Run the dependency tree command: 'inspect dependencies for github.com/elastic/package-registry'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-r727-5pf6-47r2",
  "modified" : "2026-05-06T21:56:35Z",
  "published" : "2026-04-29T00:30:22Z",
  "aliases" : [ "CVE-2026-33467" ],
  "summary" : "Elastic Package Registry has Improper Verification of Cryptographic Signature ",
  "details" : "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.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/elastic/package-registry"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.38.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33467"
  }, {
    "type" : "WEB",
    "url" : "https://discuss.elastic.co/t/elastic-package-registry-1-38-0-security-update-esa-2026-27/386081"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/elastic/package-registry"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-347" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-05-06T21:56:35Z",
    "nvd_published_at" : "2026-04-28T22:16:48Z"
  }
}