This vulnerability involves improper permission handling during buffer operations, which allows untrusted applications to create memory mappings with inappropriate permissions. This can lead to security issues related to unauthorized memory access.
A vulnerability in the Exynos modem's IMS stack involves improper handling of SDP payloads, which can cause a Denial of Service (DoS). This flaw is identified as CVE-2026-48179. No specific affected versions or patches are provided in the available data.
A vulnerability in the NR RRC component causes improper handling of messages before authentication, leading to a data abort and resulting in a denial-of-service condition.
An out-of-bounds access vulnerability exists in the Exynos modem's IMS stack caused by improper validation. This flaw could potentially lead to memory corruption or unexpected behavior within the modem's IMS functionality.
Kyverno versions from 1.11.0 up to but not including 1.19.2 contain an unbounded decompression vulnerability in the FetchSignatureBlob function. This flaw allows attackers who control registry referrers or signatures to supply highly compressed notary signature layers that decompress beyond the configured maximum payload size. Exploiting this can cause the admission controller to consume excessive memory, leading to out-of-memory (OOM) kills and denial of service.
An integer underflow vulnerability exists in the dstarCallsignToAPRS function within APRSUtils.cpp in G4KLX DStarGateway and F4FXL DStarGateway before commit 7b75de6. This occurs via an empty RS-MS1A sender field. The vulnerability has a critical severity with a CVSS 4.0 score of 9.2.
A vulnerability in the NAS Authentication Request message decoding procedure involves a missing lower bound check that causes an infinite loop, resulting in a Denial of Service condition.
A vulnerability in the LTE RRC component causes improper handling of messages received before authentication, resulting in a data abort that leads to a denial-of-service condition.
CVE-2026-33965 is a vulnerability where an attacker may send a malicious IMS message to a target device, potentially causing information exposure through the SIP message flow. No specific affected versions or patch information are provided.
A vulnerability identified as CVE-2026-33958 involves processing a malformed RRC Reconfiguration message that causes an out-of-bounds (OOB) access, leading to a denial-of-service (DoS) condition.
Kyverno versions from 1.11.0 up to but not including 1.19.2 contain an unbounded decompression vulnerability in the extractStatement function. This flaw allows remote attackers to cause denial of service by exhausting memory resources through highly compressed attestation layers. Specifically, attackers controlling registry referrer artifacts can push gzip predicate layers that exceed the maximum payload size when decompressed, leading to out-of-memory (OOM) kills of the admission controller.
Kyverno versions prior to 1.19.2 have a missing authorization vulnerability that allows namespaced Policy authors to read resources in other namespaces. This occurs through templating of generate.clone or cloneList namespace values, enabling an attacker to annotate a ConfigMap that triggers the background-controller to copy sensitive ConfigMaps from a victim namespace into the attacker's namespace. This results in unauthorized cross-tenant data disclosure.
Kyverno versions before 1.19.2 have an unchecked type assertion vulnerability in the buildStatementMap function. This flaw allows unauthenticated attackers to crash the policy engine by submitting crafted attestation statements. Specifically, attackers can push an OCI referrer manifest containing a non-string type field, which can bypass image verification when failurePolicy is set to Ignore or cause a crash-loop in the reports-controller.
Kyverno versions from 1.17.0 up to but not including 1.19.2 have a missing authorization vulnerability in the mutate-existing background processor. This flaw allows namespaced tenants to modify resources outside their own namespace by creating a NamespacedMutatingPolicy targeting Namespace objects or resources in other namespaces. Exploitation can lead to the background-controller ServiceAccount stripping Pod Security labels cluster-wide.
Kyverno versions before 1.19.2 have a vulnerability in the variable-substitution engine where an unchecked type assertion can cause the policy engine to crash. This occurs when users submit resources with non-string fields referenced by shallow substitution in policies, leading to a panic. The resulting crash causes webhook denial of service and may allow policy bypass if failurePolicy is set to Ignore.
Kyverno versions before 1.19.2 contain an authentication bypass vulnerability in the matchCertificateData function. This flaw allows attackers with a leaf certificate from a configured private trust root to bypass verifyImages subject and subjectRegExp checks if the signing certificate lacks a Subject Alternative Name (SAN). By omitting the SAN and setting the expected Fulcio issuer OID, attackers can sign malicious images that are admitted despite signer pinning.
Kyverno versions from 1.16.0 up to but not including 1.19.2 contain a vulnerability where path segments in the resource argument of resource.get() and resource.post() are not properly validated. This flaw allows namespaced CEL policies to escape their namespace boundaries. An attacker with the ability to create a NamespacedValidatingPolicy can exploit this by inserting '..' segments to read and write arbitrary cluster objects via the admission controller's ServiceAccount, potentially leading to full cluster takeover.
Kyverno versions from 1.19.1 up to but not including 1.19.2 contain a namespace isolation bypass vulnerability in the APICall Fetch() function. This occurs because the path.Clean function treats the '?' character as part of the path, allowing a crafted URLPath with query parameters to bypass namespace restrictions. Users with permission to create namespaced policies can exploit this to access cluster-scoped resources outside their namespace.
Kyverno versions from 1.17.0 up to but not including 1.19.2 contain a critical privilege escalation vulnerability. This flaw allows namespace-scoped tenants to modify resources in other namespaces by exploiting a lack of namespace checks in the NamespacedMutatingPolicy targetMatchConstraints.expression CEL output. Attackers can manipulate cluster-wide background controllers to mutate RoleBindings, Roles, NetworkPolicies, and ConfigMaps belonging to other tenants.