Vulnerability in github.com/elastic/package-registry (CVE-2026-33467)
Summary
Vulnerability in github.com/elastic/package-registry (CVE-2026-33467). Data can be tampered with by attackers. Mitigation: upgrade to 1.38.0 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-33467 has been found in github.com/elastic/package-registry.
Data can be tampered with by attackers. CVSS score: 5.9/10.
What to do: upgrade github.com/elastic/package-registry to 1.38.0 or later.
If unsure, ask your IT team or search "github.com/elastic/package-registry CVE-2026-33467" on the vendor's site.
CVE-2026-33467 (github.com/elastic/package-registry) — CWE-347 / CVSS v3 5.9
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.38.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-347) exists in github.com/elastic/package-registry.
Check the vendor advisory for the affected versions of github.com/elastic/package-registry.
Severity: Medium (CVSS 5.9/10). Data can be tampered with by attackers.
Update to 1.38.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/elastic/package-registry' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/elastic/package-registry' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/elastic/package-registryを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/elastic/package-registry to 1.38.0ステージング環境で 1.38.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- web discuss.elastic.co