Adobe DNG Software Development Kit (SDK): Out-of-bounds Read (CVE-2026-33636)
Published Sources: BSI
What is affected, what to do
A flaw was found in libpng. A remote attacker could exploit an out-of-bounds read and write vulnerability in the ARM/AArch64 Neon-optimized palette expansion path.
Update Linux to version 5.10.258, ddk to version 26.1, libpng to version 1.6.56.
- Affected
- Pnggroup Libpng
gte 1.6.36, < 1.6.56..*
- Pnggroup Libpng
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.6
Priority
XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.6
CVSS v3
Severity High on the scale from 0 to 10.
Source: BSI
0.8 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 55.3
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 69.02 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- no public PoC known
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.6 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.6
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.8 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 55.3
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · not automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 26 March 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-125, CWE-787
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- High technical severity: assess and remediate the vulnerability in vulnerability handling under Art. 21(2)(e) NIS2 and document the decision.
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- From 11.12.2027, Annex I Part II CRA requires manufacturers of affected products with digital elements to handle vulnerabilities without delay and provide security updates.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
A flaw was found in libpng. A remote attacker could exploit an out-of-bounds read and write vulnerability in the ARM/AArch64 Neon-optimized palette expansion path. This occurs when processing a final partial chunk of 8-bit paletted rows without verifying sufficient input pixels, leading to dereferencing pointers before the start of the row buffer and writing expanded pixel data to underflowed positions. This flaw can result in information disclosure and denial of service.
Source: BSI WID Portal
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Adobe | Adobe DNG Software Development Kit (SDK) |
|
|
| Arm Ltd | Arm 5th Gen GPU Architecture Kernel Driver |
|
|
| Arm Ltd | Bifrost GPU Kernel Driver |
|
|
| Arm Ltd | Valhall GPU Kernel Driver |
|
|
| Android |
|
| |
| Imagination Technologies | Graphics DDK |
|
|
| Linux | Linux |
|
|
From bundled advisories, not CVE-specific (2)
Product list of a bundled advisory that does not state which product this CVE affects.
| Affected versions | Fixed in | ||
|---|---|---|---|
| Open Source | libpng |
|
|
| Red Hat | Enterprise Linux |
|
|
Vendors and products
Affected operating systems
| Linux | ubuntu | aws | bionic |
| Linux | ubuntu | aws | jammy |
| Linux | ubuntu | aws | noble |
| Linux | ubuntu | aws | resolute |
| Linux | ubuntu | aws | xenial |
| Linux | ubuntu | aws-6.8 | jammy |
| Linux | ubuntu | aws-hwe | xenial |
| Linux | ubuntu | azure | jammy |
| Linux | ubuntu | azure | noble |
| Linux | ubuntu | azure | resolute |
| Linux | ubuntu | azure | xenial |
| Linux | ubuntu | azure-4.15 | bionic |
| Linux | ubuntu | gcp | jammy |
| Linux | ubuntu | gcp | noble |
| Linux | ubuntu | gcp | resolute |
| Linux | ubuntu | gcp | xenial |
| Linux | ubuntu | gcp-4.15 | bionic |
| Linux | ubuntu | gcp-6.8 | jammy |
| Linux | ubuntu | generic-4.15 | bionic |
| Linux | ubuntu | generic-4.15 | xenial |
| Linux | ubuntu | generic-4.4 | xenial |
| Linux | ubuntu | generic-5.4 | bionic |
| Linux | ubuntu | generic-5.4 | focal |
| Linux | ubuntu | gke | jammy |
Weakness classes (CWE)
CWE-125Out-of-bounds Read
Base
The product reads data past the end, or before the beginning, of the intended buffer.
Entry at MITRE CWE-125CWE-787Out-of-bounds Write
Base
The product writes data past the end, or before the beginning, of the intended buffer.
Entry at MITRE CWE-787
References & sources
- source.android.comdocs/security/bulletin/2026/2026-09-01
- source.android.comsecurity/bulletin/2026-09-01advisory
- android.googlesource.complatform/frameworks/base/+/4b3bf7fb29ec6e50bcfb91d96692b4536da1…fix
- imaginationtech.comgpu-driver-vulnerabilitiesVendor advisory
- support.arm.comdocumentation/111552/1-0/?lang=en
- unisoc.comen/support/product-security-bulletin/2084109408382668801
- android.googlesource.complatform/packages/modules/Nfc/+/9f4efdd67acb88de5f3450a31a85c05…fix
- docs.qualcomm.comproduct/publicresources/securitybulletin/september-2026-bulleti…
- android.googlesource.complatform/frameworks/base/+/8df772fb59b4f688f09bc94c7afc9615cfb5…fix
- android.googlesource.complatform/packages/services/Telephony/+/5ef227b0a2f76cdc6f4c8596…fix
- docs.qualcomm.comproduct/publicresources/securitybulletin/june-2026-bulletin.html
- git.codelinaro.orgclo/la/abl/tianocore/edk2/-/commit/f08125d8276c21d93a997bd03193…fix
- android.googlesource.complatform/packages/modules/Nfc/+/19fc329133fe95e5da27ebd54b6d4fb…fix
- android.googlesource.complatform/art/+/70be2043e6dbcd080b82022a3dee030de7caad80fix
- android.googlesource.complatform/packages/providers/TelephonyProvider/+/1fab99e951d5c57…fix
- android.googlesource.complatform/frameworks/base/+/8800ef252b9f59834c1e1707bfa47a5de65a…fix
- android.googlesource.complatform/frameworks/base/+/323c8b968a8821bf34149803912334be42e6…fix
- git.kernel.orgstable/c/772f99cc8d6e5d95613bce93c9624e154c1abe88euvd, Patch
- git.kernel.orgstable/c/b846fb0a73e99174f08238e083e284c0463a2102euvd, Patch
- git.kernel.orgstable/c/9a793ac19eb84f44ed759c0fce80cf29bc2a2453euvd, Patch
Linked CVEs
| High | CVE-2026-7639 | GPU DDK - Page UAF read in PMMETA_PROTECT heap memory | 7.8 | — |
| High | CVE-2026-7477 | Mali GPU Kernel Driver allows access to already freed memory | 7.8 | — |
| High | CVE-2026-7476 | Mali GPU Kernel Driver allows access to already freed memory | 7.8 | — |
| High | CVE-2026-58941 | Google Android: Out-of-Bounds Read | 7.8 | — |
| High | CVE-2026-58874 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-58848 | Google Android: Race Condition | 7.0 | — |
| High | CVE-2026-58846 | Google Android: Use-After-Free | 7.8 | — |
| High | CVE-2026-58839 | Google Android: Buffer Overflow | 7.8 | — |
| High | CVE-2026-58823 | Google Android: security vulnerability | 7.8 | — |
| Critical | CVE-2026-58822 | Google Android: Remote Code Execution | 9.8 | — |
| High | CVE-2026-58820 | Google Android: Integer Overflow | 7.8 | — |
| High | CVE-2026-5729 | Mali GPU Kernel Driver allows access to already freed memory | 7.8 | — |
| High | CVE-2026-55294 | Google Android: Heap-Based Buffer Overflow | 7.8 | — |
| Low | CVE-2026-55290 | Google Android: Out-of-Bounds Access | 3.3 | — |
| High | CVE-2026-55285 | Google Android: Out-of-Bounds Write | 7.8 | — |
| High | CVE-2026-55277 | Google Android: Out-of-Bounds Write | 8.0 | — |
| High | CVE-2026-55273 | Google Android: Improper Input Validation | 7.8 | — |
| Medium | CVE-2026-55256 | Google Android: Improper Input Validation | 6.5 | — |
| Critical | CVE-2026-52993 | Linux Kernel: Release of Invalid Pointer or Reference | 9.8 | — |
| High | CVE-2026-49932 | Google Android: Heap-Based Buffer Overflow | 7.8 | — |
| High | CVE-2026-49927 | Google Android: Out-of-Bounds Write | 7.8 | — |
| Not rated | CVE-2026-49926 | Google Android: security vulnerability | — | — |
| Critical | CVE-2026-49921 | Google Android: Heap-Based Buffer Overflow | 9.8 | — |
| High | CVE-2026-49919 | Google Android: Integer Overflow | 7.8 | — |
Show 156 more CVEs
| High | CVE-2026-49918 | Google Android: Out-of-Bounds Write | 7.8 | — |
| Not rated | CVE-2026-49913 | Google Android: security vulnerability | — | — |
| Low | CVE-2026-49895 | Google Android: Out-of-Bounds Read | 3.5 | — |
| High | CVE-2026-49887 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-49884 | Google Android: Out-of-Bounds Write | 7.8 | — |
| High | CVE-2026-49882 | Google Android: Heap-Based Buffer Overflow | 8.8 | — |
| High | CVE-2026-49881 | Google Android: Code Execution | 7.8 | — |
| High | CVE-2026-49879 | Google Android: Out-of-Bounds Write | 8.8 | — |
| High | CVE-2026-49746 | GPU DDK - Dimension Mismatch and Integer Truncation in PMRDevPhysAddrOSMem | 7.1 | — |
| High | CVE-2026-49745 | GPU DDK - Unvalidated sHWPerfCtlDMABuf GPU-VA, DMA-write into FW privdata via MMU ctx 0 | 7.8 | — |
| High | CVE-2026-49744 | GPU DDK - Unchecked ui32TracePointer in rgxfw_log_ex() | 7.8 | — |
| High | CVE-2026-49743 | Imagination Technologies Graphics DDK: Use After Free | 7.8 | — |
| High | CVE-2026-4967 | Google Android: Out-of-Bounds Read | 7.5 | — |
| High | CVE-2026-45531 | Google Android: Heap-Based Buffer Overflow | 7.8 | — |
| Not rated | CVE-2026-45529 | Google Android: security vulnerability | — | — |
| High | CVE-2026-45528 | Google Android: security vulnerability | 7.3 | — |
| Medium | CVE-2026-45527 | Google Android: Integer Overflow | 4.3 | — |
| Low | CVE-2026-45525 | Google Android: Information Disclosure | 3.3 | — |
| Low | CVE-2026-45521 | Google Android: Information Disclosure | 3.3 | — |
| High | CVE-2026-45520 | Google Android: Authentication Bypass | 7.8 | — |
| Low | CVE-2026-45519 | Google Android: Information Disclosure | 3.3 | — |
| Not rated | CVE-2026-45518 | Google Android: security vulnerability | — | — |
| Not rated | CVE-2026-45517 | Google Android: security vulnerability | — | — |
| High | CVE-2026-45515 | Google Android: Heap-Based Buffer Overflow | 7.8 | — |
| High | CVE-2026-45203 | GPU DDK - rgxfw_hwperf_ufo() re-reads psCmdHeader->ui32CmdSize after initial check, TOCTOU | 7.8 | — |
| Medium | CVE-2026-45202 | GPU DDK - Silent High-Order CMA Memory Leak & Double Free in `_FreeOSPages_Fast` | 5.5 | — |
| High | CVE-2026-45200 | GPU DDK - Double free in _FreeOSPages due to incorrect allocation flag set by _EncodeAllocationFlags | 7.8 | — |
| High | CVE-2026-45198 | GPU DDK - RGXFWIF_SYSINIT::sCorememDataStore is untrusted | 7.8 | — |
| Low | CVE-2026-45197 | GPU DDK - TOCTOU affecting psFWMemContext->uiPageCatBaseRegSet | 2.5 | — |
| High | CVE-2026-45196 | Imagination Technologies Graphics DDK: Improper Handling of Insufficient Permissions or Privileges | 7.8 | — |
| High | CVE-2026-45195 | GPU DDK - rgxfw_set_mips_fault_address(&psInit->sFaultPhysAddr) is untrusted | 7.8 | — |
| High | CVE-2026-43049 | Linux Kernel: Use-After-Free | 7.8 | — |
| High | CVE-2026-41158 | GPU DDK - Backed sparse PMRs are not handled by deferred free mechanism after shrink | 7.8 | — |
| Critical | CVE-2026-41157 | GPU DDK - OOB Write in CalculateNPOTTwiddleSparsePageMap3D | 9.8 | — |
| High | CVE-2026-41156 | GPU DDK - kernel<->fw CCB contains SYNC_PRIMITIVE_BLOCK firmware address without holding reference | 7.7 | — |
| High | CVE-2026-34196 | Imagination Technologies Graphics DDK: Use After Free | 7.8 | — |
| High | CVE-2026-34195 | Imagination Technologies Graphics DDK: Out-of-bounds Write | 8.8 | — |
| High | CVE-2026-34194 | Imagination Technologies Graphics DDK: Incorrect Pointer Scaling | 7.1 | — |
| Medium | CVE-2026-34193 | GPU DDK - Arbitrary write via UFO updates due insufficient pointer validation in rgxfw_to_ptr() | 4.3 | — |
| High | CVE-2026-34192 | GPU DDK - _MMU_AllocLevel error recovery paths leave dangling page table entries | 7.7 | — |
| High | CVE-2026-33636 | LIBPNG has ARM NEON Palette Expansion Out-of-Bounds Read on AArch64 | 7.6 | — |
| High | CVE-2026-31629 | Linux Kernel: Use-After-Free | 8.8 | — |
| Low | CVE-2026-28671 | Google Android: Race Condition | 3.3 | — |
| High | CVE-2026-28668 | Google Android: Use-After-Free | 7.8 | — |
| High | CVE-2026-28666 | Google Android: Denial of Service | 8.8 | — |
| High | CVE-2026-28664 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28663 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28662 | Google Android: Heap-Based Buffer Overflow | 8.0 | — |
| Low | CVE-2026-28660 | Google Android: Information Disclosure | 3.3 | — |
| High | CVE-2026-28658 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28657 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28656 | Google Android: security vulnerability | 7.3 | — |
| High | CVE-2026-28655 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28653 | Google Android: Out-of-Bounds Write | 7.8 | — |
| Low | CVE-2026-28652 | Google Android: Information Disclosure | 3.1 | — |
| High | CVE-2026-28650 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28644 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28642 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28639 | Google Android: Out-of-Bounds Write | 7.8 | — |
| Low | CVE-2026-28638 | Google Android: Information Disclosure | 3.3 | — |
| High | CVE-2026-28636 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28634 | Google Android: security vulnerability | 7.8 | — |
| Medium | CVE-2026-28633 | Google Android: Denial of Service | 5.5 | — |
| High | CVE-2026-28631 | Google Android: security vulnerability | 7.8 | — |
| Low | CVE-2026-28630 | Google Android: Information Disclosure | 3.3 | — |
| Medium | CVE-2026-28627 | Google Android: Information Disclosure | 4.3 | — |
| High | CVE-2026-28626 | Google Android: security vulnerability | 7.3 | — |
| High | CVE-2026-28624 | Google Android: security vulnerability | 7.8 | — |
| Low | CVE-2026-28623 | Google Android: Information Disclosure | 3.3 | — |
| Low | CVE-2026-28622 | Google Android: Information Disclosure | 3.3 | — |
| High | CVE-2026-28620 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28618 | Google Android: Heap-Based Buffer Overflow | 8.8 | — |
| Medium | CVE-2026-28617 | Google Android: Denial of Service | 5.5 | — |
| High | CVE-2026-28616 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28614 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28613 | Google Android: Improper Input Validation | 7.3 | — |
| High | CVE-2026-28612 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28611 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28609 | Google Android: Out-of-Bounds Write | 8.8 | — |
| High | CVE-2026-28607 | Google Android: security vulnerability | 7.8 | — |
| Critical | CVE-2026-28606 | Google Android: security vulnerability | 9.8 | — |
| High | CVE-2026-28604 | Google Android: Use-After-Free | 7.5 | — |
| High | CVE-2026-28603 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28602 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28600 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28599 | Google Android: security vulnerability | 7.8 | — |
| Medium | CVE-2026-28596 | Google Android: Denial of Service | 5.5 | — |
| High | CVE-2026-28594 | Google Android: Use-After-Free | 7.8 | — |
| High | CVE-2026-28593 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-28590 | Google Android: security vulnerability | 7.8 | — |
| Medium | CVE-2026-28584 | Google Android: Denial of Service | 5.5 | — |
| High | CVE-2026-28583 | Google Android: Out-of-Bounds Write | 7.8 | — |
| Low | CVE-2026-28582 | Google Android: Information Disclosure | 3.3 | — |
| Medium | CVE-2026-28581 | Google Android: NULL Pointer Dereference | 4.0 | — |
| High | CVE-2026-28572 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-27280 | DNG SDK | Out-of-bounds Write (CWE-787) | 7.8 | — |
| High | CVE-2026-25294 | Buffer Over-read in WLAN Firmware | 7.4 | — |
| Critical | CVE-2026-25289 | Stack-based Buffer Overflow in WLAN Firmware | 9.6 | — |
| High | CVE-2026-25288 | Buffer Over-read in WLAN Firmware | 7.4 | — |
| High | CVE-2026-25275 | Buffer Over-read in WLAN Firmware | 7.5 | — |
| High | CVE-2026-25260 | Time-of-check Time-of-use (TOCTOU) Race Condition in DSP Service | 7.8 | — |
| High | CVE-2026-25259 | Out-of-bounds Write in DSP Service | 7.8 | — |
| High | CVE-2026-24092 | Improper Validation of Syntactic Correctness of Input in Display | 7.2 | — |
| High | CVE-2026-24091 | Improper Validation of Syntactic Correctness of Input in Display | 7.2 | — |
| High | CVE-2026-24090 | Missing Authentication for Critical Function in HLOS | 7.1 | — |
| High | CVE-2026-24088 | Missing Authentication for Critical Function in Boot | 8.2 | — |
| High | CVE-2026-24087 | Improper Validation of Syntactic Correctness of Input in Kernel | 7.2 | — |
| High | CVE-2026-24084 | Insecure Security Identifier Mechanism in Multi-Mode Call Processor | 7.5 | — |
| High | CVE-2026-24081 | Buffer Over-read in BT Controller | 7.4 | — |
| High | CVE-2026-24080 | Buffer Copy Without Checking Size of Input in Biometrics | 7.8 | — |
| High | CVE-2026-24079 | Missing Authentication for Critical Function in Data Modem | 8.1 | — |
| High | CVE-2026-22166 | GPU DDK - Write UAF in KEGLGetPoolBuffers, WebGL reachable | 8.1 | — |
| High | CVE-2026-22164 | GPU DDK - Kernel heap OOB write in DevmemIntComputeVirtualIndicesFromLogical | 7.5 | — |
| High | CVE-2026-21734 | GPU DDK - libusc OOB write at TreeRemove during WebGPU shader compilation | 7.7 | — |
| High | CVE-2026-21733 | Imagination Technologies Graphics DDK: Improper Handling of Insufficient Permissions or Privileges | 7.3 | — |
| Critical | CVE-2026-21732 | GPU DDK - libusc OOB write at ConvertSwitchToArrayLookupBP during WebGPU shader compilation | 9.6 | — |
| High | CVE-2026-21553 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21552 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21551 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21550 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21549 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21548 | Unisoc (Shanghai) Technologies T8100/T9100/T8200/T8300: Improper Input Validation | 7.5 | — |
| High | CVE-2026-21383 | Reusing a Nonce, Key Pair in Encryption in HLOS | 7.1 | — |
| Medium | CVE-2026-20504 | MediaTek chipset: Reachable Assertion | 5.3 | — |
| Medium | CVE-2026-20503 | MediaTek chipset: Reachable Assertion | 5.3 | — |
| High | CVE-2026-20502 | MediaTek chipset: Heap-based Buffer Overflow | 8.4 | — |
| High | CVE-2026-20501 | MediaTek chipset: Heap-based Buffer Overflow | 8.4 | — |
| Medium | CVE-2026-20500 | MediaTek chipset: Improper Certificate Validation | 5.0 | — |
| Medium | CVE-2026-20497 | MediaTek chipset: Out-of-bounds Write | 6.0 | — |
| Medium | CVE-2026-20481 | MediaTek chipset: Out-of-bounds Write | 6.0 | — |
| High | CVE-2026-20479 | MediaTek chipset: Out-of-bounds Read | 7.5 | — |
| Medium | CVE-2026-20477 | MediaTek chipset: Out-of-bounds Write | 6.0 | — |
| Medium | CVE-2026-20475 | MediaTek chipset: Out-of-bounds Write | 6.0 | — |
| Medium | CVE-2026-20474 | MediaTek chipset: Time-of-check Time-of-use (TOCTOU) Race Condition | 6.0 | — |
| Medium | CVE-2026-20473 | MediaTek chipset: Use After Free | 6.0 | — |
| Medium | CVE-2026-20469 | MediaTek chipset: Write-what-where Condition | 6.0 | — |
| Medium | CVE-2026-20468 | MediaTek chipset: Out-of-bounds Write | 6.0 | — |
| Medium | CVE-2026-20467 | MediaTek chipset: Exposed Dangerous Method or Function | 6.0 | — |
| Medium | CVE-2026-20464 | MediaTek chipset: Out-of-bounds Write | 6.5 | — |
| Medium | CVE-2026-20461 | MediaTek chipset: Out-of-bounds Write | 5.3 | — |
| Medium | CVE-2026-20460 | MediaTek chipset: Authentication Bypass Using an Alternate Path or Channel | 5.3 | — |
| Medium | CVE-2026-20459 | MediaTek chipset: Authentication Bypass Using an Alternate Path or Channel | 5.3 | — |
| High | CVE-2026-20458 | MediaTek chipset: Out-of-bounds Write | 7.5 | — |
| Medium | CVE-2026-20457 | MediaTek chipset: NULL Pointer Dereference | 5.3 | — |
| Medium | CVE-2026-12387 | Mali GPU Kernel Driver allows access to already freed memory | 5.1 | — |
| Medium | CVE-2026-12285 | Mali GPU Kernel Driver allows access to already freed memory | 4.0 | — |
| High | CVE-2026-0084 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2026-0065 | Google Android: security vulnerability | 7.8 | — |
| Low | CVE-2026-0054 | Google Android: Information Disclosure | 3.3 | — |
| High | CVE-2026-0010 | Google Android: Out-of-Bounds Write | 8.4 | — |
| High | CVE-2026-0008 | Google Android: Privilege Escalation | 8.4 | — |
| Medium | CVE-2026-0001 | Mali GPU Kernel Driver allows access to already freed memory | 4.4 | — |
| Medium | CVE-2025-48651 | Google Android: Improper Input Validation | 5.5 | — |
| High | CVE-2025-48566 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2025-48565 | Google Android: security vulnerability | 7.8 | — |
| High | CVE-2025-48564 | Google Android: Race Condition | 7.0 | — |
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-33636"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-33636.svg?lang=en" alt="CVE-2026-33636 – NEOSEC Intel" height="20"></a>