Skip to main content

Elastic Package Registry EUVDEUVD-2026-26140

| CVE-2026-33467 MEDIUM
Improper Verification of Cryptographic Signature (CWE-347)
2026-04-28 security@elastic.co
5.9
CVSS 3.1 · Vendor: elastic
Share

Severity by source

Vendor (elastic) PRIMARY
5.9 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
vuln.today AI
5.9 MEDIUM

Network attack vector with AC:H for required MITM position; PR:N as no credentials needed; I:H for unchecked package substitution; C:N and A:N as no data disclosure or service disruption results.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N
SUSE
MEDIUM
qualitative

Primary rating from Vendor (elastic).

CVSS VectorVendor: elastic

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

Lifecycle Timeline

3
Analysis Generated
Jul 24, 2026 - 04:12 vuln.today
EUVD ID Assigned
Apr 28, 2026 - 22:22 euvd
EUVD-2026-26140
CVE Published
Apr 28, 2026 - 22:16 nvd
MEDIUM 5.9

DescriptionCVE.org

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.

AnalysisAI

Cryptographic signature verification bypass in Elastic Package Registry versions 0.1.0 through 1.37.0 allows an adversary-in-the-middle, or an attacker with influence over a self-hosted registry's served content, to substitute tampered packages that are accepted without triggering integrity check failures. The flaw (CWE-347) undermines supply-chain integrity for organizations running self-hosted registry instances. No active exploitation is confirmed (SSVC: exploitation none; EPSS 0.02%), but the high integrity impact and zero-privilege-required vector make patching to 1.38.0 a priority for self-hosted deployments.

Technical ContextAI

Elastic Package Registry is the distribution layer for Elastic Stack integration packages - it serves packages consumed by Kibana and related tooling, making it a supply-chain trust anchor. CWE-347 (Improper Verification of Cryptographic Signature) indicates the registry's package integrity check fails open rather than closed: when a tampered package is presented, the signature validation does not correctly reject it. The tags reference 'Jwt Attack', suggesting the signature mechanism may be JWT-based or token-based, which is consistent with improper verification of a signed assertion rather than a traditional asymmetric code-signing scheme. The full CPE cpe:2.3:a:elastic:elastic_package_registry:*:*:*:*:*:*:*:* spans all versions up to 1.37.0, with EUVD-2026-26140 bounding the range explicitly at 0.1.0-1.37.0.

RemediationAI

Upgrade Elastic Package Registry to version 1.38.0, which resolves the signature verification flaw per the vendor advisory at https://discuss.elastic.co/t/elastic-package-registry-1-38-0-security-update-esa-2026-27/386081. Note: the fix version 1.38.0 is inferred from the advisory thread title and should be confirmed against the official release notes prior to deployment. For organizations unable to upgrade immediately, restrict network access to the self-hosted registry to explicitly trusted client hosts using firewall rules or network segmentation, reducing MITM exposure - this adds operational overhead and does not address the root cause. Additionally, enforcing mutual TLS between registry clients and the server can reduce the feasibility of traffic interception, though this requires client-side certificate management. Neither compensating control remediates the underlying signature verification flaw.

CVE-2013-3900 MEDIUM
5.5 Dec 11

Why is Microsoft republishing a CVE from 2013? We are republishing CVE-2013-3900 in the Security Update Guide to update

CVE-2026-48558 CRITICAL POC
9.5 Jun 12

Authentication bypass in SimpleHelp 5.5.15 and prior (plus 6.0 pre-release builds) allows remote unauthenticated attacke

CVE-2025-59718 CRITICAL
9.8 Dec 09

Authentication bypass in Fortinet FortiOS, FortiProxy, and FortiSwitchManager allows unauthenticated remote attackers to

CVE-2025-25291 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2025-25292 CRITICAL POC
9.3 Mar 12

ruby-saml provides security assertion markup language (SAML) single sign-on (SSO) for Ruby. Rated critical severity (CVS

CVE-2022-25898 CRITICAL POC
9.8 Jul 01

The package jsrsasign before 10.5.25 are vulnerable to Improper Verification of Cryptographic Signature when JWS or JWT

CVE-2024-42004 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in Microsoft Teams (work or school) 24046.2813.2770.1094 for macOS. Rated criti

CVE-2024-41145 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the WebView.app helper app of Microsoft Teams (work or school) 24046.2813.27

CVE-2024-41138 CRITICAL POC
9.8 Dec 18

A library injection vulnerability exists in the com.microsoft.teams2.modulehost.app helper app of Microsoft Teams (work

CVE-2024-45409 CRITICAL POC
9.8 Sep 10

The Ruby SAML library is for implementing the client side of a SAML authorization. Rated critical severity (CVSS 9.8), t

CVE-2022-35929 CRITICAL POC
9.8 Aug 04

cosign is a container signing and verification utility. Rated critical severity (CVSS 9.8), this vulnerability is remote

CVE-2022-31053 CRITICAL POC
9.8 Jun 13

Biscuit is an authentication and authorization token for microservices architectures. Rated critical severity (CVSS 9.8)

Vendor StatusVendor

SUSE

Severity: Moderate
Product Status
SUSE Linux Enterprise Server 16.1 Affected
SUSE Linux Enterprise Server for SAP applications 16.1 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP5 Affected
SUSE Linux Enterprise Module for Package Hub 15 SP6 Affected
openSUSE Leap 15.5 Affected

Share

EUVD-2026-26140 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy