Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 2.15% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2019
CVE-2019-11247High confidence
Kubernetes kube-apiserver allows access to custom resources via wrong scope
Kubernetes · Kubernetes
8.1HighCVSS 3.1
Within 7 days
Fix not verifiedHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- 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 Kubernetes Kubernetes and falls inside the recorded affected range.
- Recheck the vendor advisory before scheduling a change because no verified fixed version is currently retained.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Distribution package intelligence
7 package statesRelease-specific package status
Alpine, Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
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 |
|---|---|---|---|---|
| Alpine v3.23v3.23 · community | k3s | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 0.8.0-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.22v3.22 · community | k3s | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 0.8.0-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Alpine v3.21v3.21 · community | k3s | Vendor fix publishedAlpine records a security fix at this version. An absent entry does not mean the package is unaffected. | 0.8.0-r0 | Alpine Security Database ↗Source updated 22 Oct 2026 |
| Debian trixietrixie · source | kubernetes | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.17.4-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian bookwormbookworm · source | kubernetes | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.17.4-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian forkyforky · source | kubernetes | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.17.4-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
| Debian sidsid · source | kubernetes | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.17.4-1 | Debian Security Tracker ↗Source updated 23 Oct 2026 |
Open-source package ranges3 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 |
|---|---|---|---|
| gok8s.io/apiextensions-apiserver | >= 0.7.0, < 0.13.9 | 0.13.9 | GitHub advisory ↗github reviewed aggregator · 25 Sep 2023 |
| gok8s.io/apiextensions-apiserver | >= 0.14.0, < 0.14.5 | 0.14.5 | GitHub advisory ↗github reviewed aggregator · 25 Sep 2023 |
| gok8s.io/apiextensions-apiserver | >= 0.15.0, < 0.15.2 | 0.15.2 | GitHub advisory ↗github reviewed aggregator · 25 Sep 2023 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Fix not verified01
What, why and how
The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.
What
The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.
Why
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12.
Why
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
How
An attacker operating through a network path may attempt exploitation with low privileges. 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 → Improper Input Validation → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- 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-20 ↗
CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
- 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:L/UI:N/S:U/C:H/I:H/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.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.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 not verified
- Affected
- Kubernetes: prior to 1.13.9, prior to 1.14.5, prior to 1.15.2, 1.7, 1.8, 1.9, 1.10, 1.11, 1.12
- Fixed
- No fixed version is explicitly recorded in the structured CVE data.
- Action
- No verified patch reference is present in the current structured sources. Check the vendor advisory before making a change.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 29 Aug 2019 · Last source change 16 Sept 2024, 18:04 UTC · CWE-20 · Improper Input Validation
CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source FIRST · tracked since 2026-09-01
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2022-3812
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- ENISA EUVD mappingEUVD-2022-3812 was added to the official ENISA EUVD mapping for this CVE.ENISA EUVD ↗
- Before
- not recorded
- After
- {"euvdId":"EUVD-2022-3812"}
- Vendor guidanceAuthoritative vendor guidance changed: removed vendor advisory: access.redhat.com/RHBA-2019:2816; removed vendor advisory: access.redhat.com/RHBA-2019:2824; 2 further removals.CNA ↗
- Before
- vendor advisory: access.redhat.com/RHBA-2019:2816 · vendor advisory: access.redhat.com/RHBA-2019:2824 · vendor advisory: access.redhat.com/RHSA-2019:2690 · 1 more references
- After
- no authoritative guidance recorded
- SeveritySeverity changed from Medium to High.NIST NVD ↗
- Before
- Medium
- After
- High
- CVSS scoreCVSS score changed from 5.0 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L) to 8.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N).NIST NVD ↗
- Before
- 5.0 (CVSS 3.0 · CNA · CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L)
- After
- 8.1 (CVSS 3.1 · NIST NVD · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N)
- Catalogue recordCVE added to the BlackTree catalogue.CNA ↗
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.