Evidence used
- No CISA KEV confirmation is currently recorded.
- The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
- EPSS is 0.27% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-44283High confidence
etcd: Read access via PrevKv in etcd transactions may bypass RBAC authorization checks
etcd-io · etcd
Official source article: GitHub GHSA-X35M-3GP4-4FH5 ↗. Check the applicable product and release in the original source.
0.0NoneCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productThe structured sources do not provide enough evidence for a stronger action window. Track vendor updates and assess local exposure. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityNone→Operational priority:None, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs etcd-io etcd and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Debian Security Tracker: 2 affected package states with no published fix
Distribution package intelligence
5 package statesRelease-specific package status
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
Package result overrides the generic status
BlackTree has verified remediation for at least one product or source, but the relevant distribution still reports no fixed package for 2 affected package states shown here. Treat those rows as affected with no fix until that distribution publishes a fixed version.
Repository candidate not checked
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | etcd | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | etcd | Affected, no fix publishedDebian currently tracks this release as open. | Not published in this feed | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | etcd | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.5.16-11 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | etcd | Vendor fix publishedDebian records a fixed source-package version for this release. | 3.5.16-11 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · esm-apps | etcd | Under evaluationCanonical reports that the package might be affected and still needs evaluation or fixing. | Not published in this feed | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
Open-source package ranges6 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Gogo.etcd.io/etcd | SEMVER: introduced 0; fixed 3.4.44 | 3.4.44 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogo.etcd.io/etcd/v3 | SEMVER: introduced 3.6.0; fixed 3.6.11 | 3.6.11 | OSV record ↗aggregator derived · 10 Sep 2026 |
| Gogo.etcd.io/etcd/v3 | SEMVER: introduced 3.5.0; fixed 3.5.30 | 3.5.30 | OSV record ↗aggregator derived · 10 Sep 2026 |
| gogo.etcd.io/etcd | <= 3.4.43 | 3.4.44 | GitHub advisory ↗upstream repository advisory · 14 May 2026 |
| gogo.etcd.io/etcd/v3 | >= 3.6.0, <= 3.6.10 | 3.6.11 | GitHub advisory ↗upstream repository advisory · 14 May 2026 |
| gogo.etcd.io/etcd/v3 | >= 3.5.0, <= 3.5.29 | 3.5.30 | GitHub advisory ↗upstream repository advisory · 14 May 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-44283 · CSAF 2.0 · revision 3 · finalRed Hat Product Securityetcd: etcd: Authenticated user can bypass RBAC for unauthorized data access
The vendor explicitly identifies these products as affected by this CVE.
- openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4
- etcd as a component of Red Hat OpenStack Platform 16.2
- etcd.src as a component of Red Hat OpenStack Platform 16.2
- rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2
- etcd as a component of Red Hat OpenStack Platform 17.1
- etcd.src as a component of Red Hat OpenStack Platform 17.1
- rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1
- Summary
- A flaw was found in etcd, a distributed key-value store. An authenticated user, without sufficient read or lease-related permissions, could bypass Role-Based Access Control (RBAC) authorization checks. This bypass occurs during transaction operations involving PrevKv or lease attachment in Put requests, potentially leading to unauthorized data access or lease attachment.
- Remediation
- For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
The structured sources do not provide enough evidence for a stronger action window. Track vendor updates and assess local exposure. Verified remediation exists for at least one product or source, but 2 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.
What
etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
etcd is a distributed key-value store for the data of a distributed system. Prior to 3.4.44, 3.5.30, and 3.6.11, a vulnerability in etcd allows read access via PrevKv, or lease attachment in Put requests within transaction operations, to bypass RBAC authorization checks. An authenticated user without sufficient read or lease-related permissions may be able to access unauthorized data or attach leases by invoking transaction operations with these features enabled. This vulnerability is fixed in 3.4.44, 3.5.30, and 3.6.11.
Why
The application performs an authorisation check, but it does not correctly enforce the required permission boundary.
How
An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Incorrect Authorization → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-863 ↗
CWE-863: Incorrect Authorization. The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:NCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.ANoneAvailability impact: No direct loss is represented by this metric.- Post-exploitation / living off the land
- No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4
- etcd as a component of Red Hat OpenStack Platform 16.2
- etcd.src as a component of Red Hat OpenStack Platform 16.2
- rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2
- etcd as a component of Red Hat OpenStack Platform 17.1
- etcd.src as a component of Red Hat OpenStack Platform 17.1
- rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1
- Fixed
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04
Evidence and provenance
Published 14 May 2026 · Last source change 16 May 2026, 00:40 UTC · CWE-863 · Incorrect Authorization
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-30345
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- < 3.4.44; >= 3.5.0, <= 3.5.29; >= 3.6.0, <= 3.6.10 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- < 3.4.44; >= 3.5.0, <= 3.5.29; >= 3.6.0, <= 3.6.10 · Fixed: For details on how to apply this update, which includes the changes described in this advisory, refer to: https://images.redhat.com/
- Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-44283 to remediation: access.redhat.com/CVE-2026-44283.Red Hat Product Security ↗
- Before
- remediation: access.redhat.com/CVE-2026-44283
- After
- remediation: access.redhat.com/CVE-2026-44283
- Remediation statusRemediation status changed from Mitigation available to Patch available.Red Hat Product Security ↗
- Before
- Mitigation available
- After
- Patch available
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- etcd.src as a component of Red Hat Hardened Images; openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4; etcd as a component of Red Hat OpenStack Platform 16.2; etcd.src as a component of Red Hat OpenStack Platform 16.2; rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2; etcd as a component of Red Hat OpenStack Platform 17.1; etcd.src as a component of Red Hat OpenStack Platform 17.1; rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1
- After
- openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4; etcd as a component of Red Hat OpenStack Platform 16.2; etcd.src as a component of Red Hat OpenStack Platform 16.2; rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2; etcd as a component of Red Hat OpenStack Platform 17.1; etcd.src as a component of Red Hat OpenStack Platform 17.1; rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1 · Fixed: etcd-0:3.7.1-0.1.hum1@aarch64 as a component of Red Hat Hardened Images; etcd-0:3.7.1-0.1.hum1@src as a component of Red Hat Hardened Images; etcd-0:3.7.1-0.1.hum1@x86_64 as a component of Red Hat Hardened Images
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4; etcd as a component of Red Hat OpenStack Platform 16.2; etcd.src as a component of Red Hat OpenStack Platform 16.2; rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2; etcd as a component of Red Hat OpenStack Platform 17.1; etcd.src as a component of Red Hat OpenStack Platform 17.1; rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1
- After
- etcd.src as a component of Red Hat Hardened Images; openshift4/ose-etcd-rhel9 as a component of Red Hat OpenShift Container Platform 4; etcd as a component of Red Hat OpenStack Platform 16.2; etcd.src as a component of Red Hat OpenStack Platform 16.2; rhosp-rhel8/openstack-etcd as a component of Red Hat OpenStack Platform 16.2; etcd as a component of Red Hat OpenStack Platform 17.1; etcd.src as a component of Red Hat OpenStack Platform 17.1; rhosp-rhel9/openstack-etcd as a component of Red Hat OpenStack Platform 17.1
CVE published
Mitigation reference recorded
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.