Action not permitted
Modal body text goes here.
Modal Title
Modal Body
CVE-2026-22795 (GCVE-0-2026-22795)
Vulnerability from cvelistv5 – Published: 2026-01-27 16:01 – Updated: 2026-10-15 01:12- CWE-754 - Improper Check for Unusual or Exceptional Conditions
| Vendor | Product | Version | |
|---|---|---|---|
| OpenSSL | OpenSSL |
Affected:
3.6.0 , < 3.6.1
(semver)
Affected: 3.5.0 , < 3.5.5 (semver) Affected: 3.4.0 , < 3.4.4 (semver) Affected: 3.3.0 , < 3.3.6 (semver) Affected: 3.0.0 , < 3.0.19 (semver) Affected: 1.1.1 , < 1.1.1ze (custom) |
|
| Siemens | SIMATIC S7-1500 TM MFP - GNU/Linux subsystem |
Affected:
0 , < *
(custom)
|
{
"containers": {
"adp": [
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-22795",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-01-28T20:03:18.604129Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-01-29T18:13:37.371Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
},
{
"affected": [
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 TM MFP - GNU/Linux subsystem",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-15T01:12:20.101Z",
"orgId": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e",
"shortName": "siemens-SADP"
},
"references": [
{
"url": "https://cert-portal.siemens.com/productcert/html/ssa-265688.html"
}
],
"x_adpType": "supplier"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "3.6.1",
"status": "affected",
"version": "3.6.0",
"versionType": "semver"
},
{
"lessThan": "3.5.5",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.4.4",
"status": "affected",
"version": "3.4.0",
"versionType": "semver"
},
{
"lessThan": "3.3.6",
"status": "affected",
"version": "3.3.0",
"versionType": "semver"
},
{
"lessThan": "3.0.19",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1ze",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Luigino Camastra (Aisle Research)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Bob Beck"
}
],
"datePublic": "2026-01-27T14:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: An invalid or NULL pointer dereference can happen in\u003cbr\u003ean application processing a malformed PKCS#12 file.\u003cbr\u003e\u003cbr\u003eImpact summary: An application processing a malformed PKCS#12 file can be\u003cbr\u003ecaused to dereference an invalid or NULL pointer on memory read, resulting\u003cbr\u003ein a Denial of Service.\u003cbr\u003e\u003cbr\u003eA type confusion vulnerability exists in PKCS#12 parsing code where\u003cbr\u003ean ASN1_TYPE union member is accessed without first validating the type,\u003cbr\u003ecausing an invalid pointer read.\u003cbr\u003e\u003cbr\u003eThe location is constrained to a 1-byte address space, meaning any\u003cbr\u003eattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u003cbr\u003eThis range corresponds to the zero page, which is unmapped on most modern\u003cbr\u003eoperating systems and will reliably result in a crash, leading only to a\u003cbr\u003eDenial of Service. Exploiting this issue also requires a user or application\u003cbr\u003eto process a maliciously crafted PKCS#12 file. It is uncommon to accept\u003cbr\u003euntrusted PKCS#12 files in applications as they are usually used to store\u003cbr\u003eprivate keys which are trusted by definition. For these reasons, the issue\u003cbr\u003ewas assessed as Low severity.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u003cbr\u003eas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u003cbr\u003e\u003cbr\u003eOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u003cbr\u003e\u003cbr\u003eOpenSSL 1.0.2 is not affected by this issue."
}
],
"value": "Issue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-754",
"description": "CWE-754 Improper Check for Unusual or Exceptional Conditions",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-01-27T16:01:27.320Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20260127.txt"
},
{
"name": "3.6.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2"
},
{
"name": "3.5.5 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4"
},
{
"name": "3.4.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12"
},
{
"name": "3.3.6 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e"
},
{
"name": "3.0.19 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Missing ASN1_TYPE validation in PKCS#12 parsing",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-22795",
"datePublished": "2026-01-27T16:01:27.320Z",
"dateReserved": "2026-01-09T18:54:13.570Z",
"dateUpdated": "2026-10-15T01:12:20.101Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-22795",
"date": "2026-11-19",
"epss": "0.00179",
"percentile": "0.07565"
},
"microsoft_vex": {
"current_release_date": "2026-11-16T22:53:28.000Z",
"cve": "CVE-2026-22795",
"id": "msrc_CVE-2026-22795",
"initial_release_date": "2026-10-11T01:09:13.000Z",
"product_status:fixed": "1",
"product_status:known_affected": "1",
"product_status:known_not_affected": "1",
"product_status:under_investigation": "1",
"source": "Microsoft CSAF VEX",
"status": "final",
"title": "Missing ASN1_TYPE validation in PKCS#12 parsing",
"url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-22795.json",
"version": "4"
},
"redhat_vex": {
"aggregate_severity": "Low",
"current_release_date": "2026-11-07T11:17:44+00:00",
"cve": "CVE-2026-22795",
"id": "CVE-2026-22795",
"initial_release_date": "2026-01-27T00:00:00+00:00",
"product_status:fixed": "134",
"product_status:known_affected": "54",
"product_status:known_not_affected": "5",
"source": "Red Hat CSAF VEX",
"status": "final",
"title": "openssl: OpenSSL: Denial of Service due to type confusion in PKCS#12 file processing",
"url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-22795.json",
"version": "3"
},
"vulnrichment": {
"containers": {
"adp": [
{
"affected": [
{
"defaultStatus": "unknown",
"product": "SIMATIC S7-1500 TM MFP - GNU/Linux subsystem",
"vendor": "Siemens",
"versions": [
{
"lessThan": "*",
"status": "affected",
"version": "0",
"versionType": "custom"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-15T01:12:20.101Z",
"orgId": "0b142b55-0307-4c5a-b3c9-f314f3fb7c5e",
"shortName": "siemens-SADP"
},
"references": [
{
"url": "https://cert-portal.siemens.com/productcert/html/ssa-265688.html"
}
],
"x_adpType": "supplier"
},
{
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "LOCAL",
"availabilityImpact": "HIGH",
"baseScore": 5.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "NONE",
"integrityImpact": "NONE",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H",
"version": "3.1"
}
},
{
"other": {
"content": {
"id": "CVE-2026-22795",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-01-28T20:03:18.604129Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-01-28T20:03:22.912Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "OpenSSL",
"vendor": "OpenSSL",
"versions": [
{
"lessThan": "3.6.1",
"status": "affected",
"version": "3.6.0",
"versionType": "semver"
},
{
"lessThan": "3.5.5",
"status": "affected",
"version": "3.5.0",
"versionType": "semver"
},
{
"lessThan": "3.4.4",
"status": "affected",
"version": "3.4.0",
"versionType": "semver"
},
{
"lessThan": "3.3.6",
"status": "affected",
"version": "3.3.0",
"versionType": "semver"
},
{
"lessThan": "3.0.19",
"status": "affected",
"version": "3.0.0",
"versionType": "semver"
},
{
"lessThan": "1.1.1ze",
"status": "affected",
"version": "1.1.1",
"versionType": "custom"
}
]
}
],
"credits": [
{
"lang": "en",
"type": "reporter",
"value": "Luigino Camastra (Aisle Research)"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Bob Beck"
}
],
"datePublic": "2026-01-27T14:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "Issue summary: An invalid or NULL pointer dereference can happen in\u003cbr\u003ean application processing a malformed PKCS#12 file.\u003cbr\u003e\u003cbr\u003eImpact summary: An application processing a malformed PKCS#12 file can be\u003cbr\u003ecaused to dereference an invalid or NULL pointer on memory read, resulting\u003cbr\u003ein a Denial of Service.\u003cbr\u003e\u003cbr\u003eA type confusion vulnerability exists in PKCS#12 parsing code where\u003cbr\u003ean ASN1_TYPE union member is accessed without first validating the type,\u003cbr\u003ecausing an invalid pointer read.\u003cbr\u003e\u003cbr\u003eThe location is constrained to a 1-byte address space, meaning any\u003cbr\u003eattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\u003cbr\u003eThis range corresponds to the zero page, which is unmapped on most modern\u003cbr\u003eoperating systems and will reliably result in a crash, leading only to a\u003cbr\u003eDenial of Service. Exploiting this issue also requires a user or application\u003cbr\u003eto process a maliciously crafted PKCS#12 file. It is uncommon to accept\u003cbr\u003euntrusted PKCS#12 files in applications as they are usually used to store\u003cbr\u003eprivate keys which are trusted by definition. For these reasons, the issue\u003cbr\u003ewas assessed as Low severity.\u003cbr\u003e\u003cbr\u003eThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\u003cbr\u003eas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\u003cbr\u003e\u003cbr\u003eOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\u003cbr\u003e\u003cbr\u003eOpenSSL 1.0.2 is not affected by this issue."
}
],
"value": "Issue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue."
}
],
"metrics": [
{
"format": "other",
"other": {
"content": {
"text": "Low"
},
"type": "https://openssl-library.org/policies/general/security-policy/"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-754",
"description": "CWE-754 Improper Check for Unusual or Exceptional Conditions",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-01-27T16:01:27.320Z",
"orgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"shortName": "openssl"
},
"references": [
{
"name": "OpenSSL Advisory",
"tags": [
"vendor-advisory"
],
"url": "https://openssl-library.org/news/secadv/20260127.txt"
},
{
"name": "3.6.1 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/ef2fb66ec571564d64d1c74a12e388a2a54d05d2"
},
{
"name": "3.5.5 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/2502e7b7d4c0cf4f972a881641fe09edc67aeec4"
},
{
"name": "3.4.4 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/7bbca05be55b129651d9df4bdb92becc45002c12"
},
{
"name": "3.3.6 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/eeee3cbd4d682095ed431052f00403004596373e"
},
{
"name": "3.0.19 git commit",
"tags": [
"patch"
],
"url": "https://github.com/openssl/openssl/commit/572844beca95068394c916626a6d3a490f831a49"
}
],
"source": {
"discovery": "UNKNOWN"
},
"title": "Missing ASN1_TYPE validation in PKCS#12 parsing",
"x_generator": {
"engine": "Vulnogram 0.2.0"
}
}
},
"cveMetadata": {
"assignerOrgId": "3a12439a-ef3a-4c79-92e6-6081a721f1e5",
"assignerShortName": "openssl",
"cveId": "CVE-2026-22795",
"datePublished": "2026-01-27T16:01:27.320Z",
"dateReserved": "2026-01-09T18:54:13.570Z",
"dateUpdated": "2026-10-15T01:12:20.101Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
CERTFR-2026-AVI-0905
Vulnerability from certfr_avis - Published: 2026-07-21 - Updated: 2026-07-24
De multiples vulnérabilités ont été découvertes dans Tenable Security Center. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une injection SQL (SQLi) et un contournement de la politique de sécurité.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Tenable | Security Center | Security Center sans le correctif de sécurité Patch SC202607.1 |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Security Center sans le correctif de s\u00e9curit\u00e9 Patch SC202607.1",
"product": {
"name": "Security Center",
"vendor": {
"name": "Tenable",
"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-66199",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66199"
},
{
"name": "CVE-2026-23479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23479"
},
{
"name": "CVE-2026-6474",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6474"
},
{
"name": "CVE-2026-6472",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6472"
},
{
"name": "CVE-2025-15469",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15469"
},
{
"name": "CVE-2026-6479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6479"
},
{
"name": "CVE-2026-7261",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7261"
},
{
"name": "CVE-2026-6104",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6104"
},
{
"name": "CVE-2025-69419",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69419"
},
{
"name": "CVE-2026-6735",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6735"
},
{
"name": "CVE-2025-15467",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15467"
},
{
"name": "CVE-2026-2006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
},
{
"name": "CVE-2026-6637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6637"
},
{
"name": "CVE-2026-6473",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6473"
},
{
"name": "CVE-2026-2005",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
},
{
"name": "CVE-2026-22795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
},
{
"name": "CVE-2026-33857",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33857"
},
{
"name": "CVE-2025-69421",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69421"
},
{
"name": "CVE-2026-25589",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25589"
},
{
"name": "CVE-2025-14179",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14179"
},
{
"name": "CVE-2026-6638",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6638"
},
{
"name": "CVE-2026-25588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25588"
},
{
"name": "CVE-2026-22796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
},
{
"name": "CVE-2026-7568",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7568"
},
{
"name": "CVE-2026-6722",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6722"
},
{
"name": "CVE-2026-23918",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23918"
},
{
"name": "CVE-2026-24072",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24072"
},
{
"name": "CVE-2026-6478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6478"
},
{
"name": "CVE-2026-7258",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7258"
},
{
"name": "CVE-2026-23631",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23631"
},
{
"name": "CVE-2026-64880",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64880"
},
{
"name": "CVE-2026-64877",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64877"
},
{
"name": "CVE-2026-6475",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6475"
},
{
"name": "CVE-2026-25243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25243"
},
{
"name": "CVE-2026-64881",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64881"
},
{
"name": "CVE-2025-68160",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
},
{
"name": "CVE-2026-6477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6477"
},
{
"name": "CVE-2025-69418",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
},
{
"name": "CVE-2025-15468",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15468"
},
{
"name": "CVE-2026-34032",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34032"
},
{
"name": "CVE-2026-34059",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34059"
},
{
"name": "CVE-2026-42371",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42371"
},
{
"name": "CVE-2025-11187",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11187"
},
{
"name": "CVE-2026-2003",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2003"
},
{
"name": "CVE-2026-7259",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7259"
},
{
"name": "CVE-2025-68121",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68121"
},
{
"name": "CVE-2025-61726",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61726"
},
{
"name": "CVE-2026-64878",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64878"
},
{
"name": "CVE-2026-7262",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7262"
},
{
"name": "CVE-2026-33523",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33523"
},
{
"name": "CVE-2026-2004",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
},
{
"name": "CVE-2026-7263",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7263"
},
{
"name": "CVE-2025-69420",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69420"
},
{
"name": "CVE-2026-64879",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64879"
}
],
"initial_release_date": "2026-07-21T00:00:00",
"last_revision_date": "2026-07-24T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-0905",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-07-21T00:00:00.000000"
},
{
"description": "Ajout de plusieurs identifiants CVE.",
"revision_date": "2026-07-24T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Injection SQL (SQLi)"
},
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Tenable Security Center. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une injection SQL (SQLi) et un contournement de la politique de s\u00e9curit\u00e9.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Tenable Security Center",
"vendor_advisories": [
{
"published_at": "2026-07-20",
"title": "Bulletin de s\u00e9curit\u00e9 Tenable tns-2026-19",
"url": "https://www.tenable.com/security/tns-2026-19"
}
]
}
CERTFR-2026-AVI-0958
Vulnerability from certfr_avis - Published: 2026-07-31 - Updated: 2026-07-31
De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| IBM | Db2 | Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions v4.8 à v5.3.x antérieures à v5.4 patch 3 | ||
| IBM | AIX | AIX versions 7.3.x sans le correctif de sécurité curl_fix11.tar | ||
| IBM | QRadar | QRadar Data Synchronization App versions antérieures à 4.0.0 | ||
| IBM | QRadar | QRadar Pulse App versions antérieures à 2.2.17 | ||
| IBM | WebSphere Application Server | WebSphere Application Server versions 9.0.x sans les correctifs de sécurité temporaires antérieures à 9.0.5.29 (disponibilité prévue pour le troisième trimestre 2026) | ||
| IBM | Sterling Control Center | Sterling Control Center versions 6.3.1.0 sans le correctif iFix10 | ||
| IBM | WebSphere Application Server | WebSphere Application Server versions 8.5.x sans les correctifs de sécurité temporaires antérieures à 8.5.5.31 (disponibilité prévue pour le troisième trimestre 2026) | ||
| IBM | Sterling Control Center | Sterling Control Center versions 6.4.2.0 sans le correctif iFix05 | ||
| IBM | Sterling | Sterling External Authentication Server versions 6.1.x antérieures à 6.1.1.4 GA | ||
| IBM | QRadar | QRadar SIEM versions 7.5.x antérieures à 7.5.0 UP15 IF05 | ||
| IBM | Sterling B2B Integrator | Sterling B2B Integrator et Sterling File Gateway versions 6.2.0.x antérieures à 6.2.0.6_1 | ||
| IBM | Sterling B2B Integrator | Sterling B2B Integrator et Sterling File Gateway versions 6.2.1.x antérieures à 6.2.1.2 | ||
| IBM | Sterling Control Center | Sterling Control Center versions 6.4.1.0 sans le correctif iFix04 | ||
| IBM | Sterling B2B Integrator | Sterling B2B Integrator et Sterling File Gateway versions 6.2.2.x antérieures à 6.2.2.1 | ||
| IBM | WebSphere Application Server | WebSphere Application Server Liberty versions antérieures à 26.0.0.9 (disponibilité prévue pour le troisième trimestre 2026) |
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Db2 on Cloud Pak for Data and Db2 Warehouse on Cloud Pak for Data versions v4.8 \u00e0 v5.3.x ant\u00e9rieures \u00e0 v5.4 patch 3",
"product": {
"name": "Db2",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "AIX versions 7.3.x sans le correctif de s\u00e9curit\u00e9 curl_fix11.tar",
"product": {
"name": "AIX",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "QRadar Data Synchronization App versions ant\u00e9rieures \u00e0 4.0.0",
"product": {
"name": "QRadar",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "QRadar Pulse App versions ant\u00e9rieures \u00e0 2.2.17",
"product": {
"name": "QRadar",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "WebSphere Application Server versions 9.0.x sans les correctifs de s\u00e9curit\u00e9 temporaires ant\u00e9rieures \u00e0 9.0.5.29 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
"product": {
"name": "WebSphere Application Server",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling Control Center versions 6.3.1.0 sans le correctif iFix10",
"product": {
"name": "Sterling Control Center",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "WebSphere Application Server versions 8.5.x sans les correctifs de s\u00e9curit\u00e9 temporaires ant\u00e9rieures \u00e0 8.5.5.31 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
"product": {
"name": "WebSphere Application Server",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling Control Center versions 6.4.2.0 sans le correctif iFix05",
"product": {
"name": "Sterling Control Center",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling External Authentication Server versions 6.1.x ant\u00e9rieures \u00e0 6.1.1.4 GA",
"product": {
"name": "Sterling",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "QRadar SIEM versions 7.5.x ant\u00e9rieures \u00e0 7.5.0 UP15 IF05",
"product": {
"name": "QRadar",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.0.x ant\u00e9rieures \u00e0 6.2.0.6_1",
"product": {
"name": "Sterling B2B Integrator",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.1.x ant\u00e9rieures \u00e0 6.2.1.2",
"product": {
"name": "Sterling B2B Integrator",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling Control Center versions 6.4.1.0 sans le correctif iFix04",
"product": {
"name": "Sterling Control Center",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "Sterling B2B Integrator et Sterling File Gateway versions 6.2.2.x ant\u00e9rieures \u00e0 6.2.2.1",
"product": {
"name": "Sterling B2B Integrator",
"vendor": {
"name": "IBM",
"scada": false
}
}
},
{
"description": "WebSphere Application Server Liberty versions ant\u00e9rieures \u00e0 26.0.0.9 (disponibilit\u00e9 pr\u00e9vue pour le troisi\u00e8me trimestre 2026)",
"product": {
"name": "WebSphere Application Server",
"vendor": {
"name": "IBM",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-5588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5588"
},
{
"name": "CVE-2026-45505",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45505"
},
{
"name": "CVE-2025-66199",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66199"
},
{
"name": "CVE-2026-3449",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3449"
},
{
"name": "CVE-2026-59871",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59871"
},
{
"name": "CVE-2026-42588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42588"
},
{
"name": "CVE-2026-33845",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33845"
},
{
"name": "CVE-2026-44025",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44025"
},
{
"name": "CVE-2026-42253",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42253"
},
{
"name": "CVE-2026-39830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39830"
},
{
"name": "CVE-2026-42041",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42041"
},
{
"name": "CVE-2026-42508",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42508"
},
{
"name": "CVE-2026-41716",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41716"
},
{
"name": "CVE-2026-16184",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16184"
},
{
"name": "CVE-2026-15328",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15328"
},
{
"name": "CVE-2025-15469",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15469"
},
{
"name": "CVE-2020-13956",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-13956"
},
{
"name": "CVE-2025-47944",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47944"
},
{
"name": "CVE-2025-56200",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-56200"
},
{
"name": "CVE-2026-59874",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59874"
},
{
"name": "CVE-2026-42258",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42258"
},
{
"name": "CVE-2026-7769",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7769"
},
{
"name": "CVE-2026-30827",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-30827"
},
{
"name": "CVE-2026-22752",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22752"
},
{
"name": "CVE-2026-39833",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39833"
},
{
"name": "CVE-2025-22228",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-22228"
},
{
"name": "CVE-2026-8458",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8458"
},
{
"name": "CVE-2026-2391",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2391"
},
{
"name": "CVE-2026-1605",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1605"
},
{
"name": "CVE-2026-46605",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46605"
},
{
"name": "CVE-2026-22013",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22013"
},
{
"name": "CVE-2026-53655",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53655"
},
{
"name": "CVE-2026-29145",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29145"
},
{
"name": "CVE-2026-22018",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22018"
},
{
"name": "CVE-2026-39832",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39832"
},
{
"name": "CVE-2020-13955",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-13955"
},
{
"name": "CVE-2026-39829",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39829"
},
{
"name": "CVE-2026-41988",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41988"
},
{
"name": "CVE-2026-14528",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14528"
},
{
"name": "CVE-2026-6357",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6357"
},
{
"name": "CVE-2026-23745",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23745"
},
{
"name": "CVE-2026-2006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
},
{
"name": "CVE-2026-53550",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-53550"
},
{
"name": "CVE-2026-41721",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41721"
},
{
"name": "CVE-2026-54905",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54905"
},
{
"name": "CVE-2026-0994",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0994"
},
{
"name": "CVE-2026-49157",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49157"
},
{
"name": "CVE-2021-47154",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-47154"
},
{
"name": "CVE-2026-44494",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44494"
},
{
"name": "CVE-2026-54899",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54899"
},
{
"name": "CVE-2026-39834",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39834"
},
{
"name": "CVE-2025-15284",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15284"
},
{
"name": "CVE-2026-41635",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41635"
},
{
"name": "CVE-2026-46595",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46595"
},
{
"name": "CVE-2026-54901",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54901"
},
{
"name": "CVE-2026-42036",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42036"
},
{
"name": "CVE-2026-2005",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
},
{
"name": "CVE-2022-39135",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-39135"
},
{
"name": "CVE-2026-39821",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39821"
},
{
"name": "CVE-2026-33558",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33558"
},
{
"name": "CVE-2026-33846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33846"
},
{
"name": "CVE-2021-23337",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-23337"
},
{
"name": "CVE-2026-5758",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5758"
},
{
"name": "CVE-2026-34500",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34500"
},
{
"name": "CVE-2026-54502",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54502"
},
{
"name": "CVE-2026-22795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
},
{
"name": "CVE-2026-29146",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29146"
},
{
"name": "CVE-2026-34043",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34043"
},
{
"name": "CVE-2025-64718",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-64718"
},
{
"name": "CVE-2026-9277",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9277"
},
{
"name": "CVE-2026-27136",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27136"
},
{
"name": "CVE-2025-62718",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-62718"
},
{
"name": "CVE-2026-4800",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4800"
},
{
"name": "CVE-2026-10536",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10536"
},
{
"name": "CVE-2026-41844",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41844"
},
{
"name": "CVE-2026-8932",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8932"
},
{
"name": "CVE-2026-4424",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4424"
},
{
"name": "CVE-2026-45292",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45292"
},
{
"name": "CVE-2024-38820",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38820"
},
{
"name": "CVE-2026-40356",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40356"
},
{
"name": "CVE-2026-15325",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15325"
},
{
"name": "CVE-2026-14976",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14976"
},
{
"name": "CVE-2026-5598",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5598"
},
{
"name": "CVE-2026-42256",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42256"
},
{
"name": "CVE-2026-42033",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42033"
},
{
"name": "CVE-2025-59375",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-59375"
},
{
"name": "CVE-2026-54906",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54906"
},
{
"name": "CVE-2026-34040",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34040"
},
{
"name": "CVE-2026-42035",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42035"
},
{
"name": "CVE-2026-41842",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41842"
},
{
"name": "CVE-2026-44495",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44495"
},
{
"name": "CVE-2026-41695",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41695"
},
{
"name": "CVE-2026-14512",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14512"
},
{
"name": "CVE-2026-11856",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11856"
},
{
"name": "CVE-2026-44160",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44160"
},
{
"name": "CVE-2026-42009",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42009"
},
{
"name": "CVE-2026-33750",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33750"
},
{
"name": "CVE-2026-5038",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5038"
},
{
"name": "CVE-2026-34478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34478"
},
{
"name": "CVE-2026-2359",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2359"
},
{
"name": "CVE-2026-42043",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42043"
},
{
"name": "CVE-2025-11143",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11143"
},
{
"name": "CVE-2026-34480",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34480"
},
{
"name": "CVE-2026-59869",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59869"
},
{
"name": "CVE-2025-7783",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-7783"
},
{
"name": "CVE-2025-12758",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12758"
},
{
"name": "CVE-2026-40175",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40175"
},
{
"name": "CVE-2026-5079",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5079"
},
{
"name": "CVE-2026-5795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5795"
},
{
"name": "CVE-2024-23953",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-23953"
},
{
"name": "CVE-2025-68161",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68161"
},
{
"name": "CVE-2026-44930",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44930"
},
{
"name": "CVE-2026-14974",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14974"
},
{
"name": "CVE-2024-29869",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-29869"
},
{
"name": "CVE-2026-42010",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42010"
},
{
"name": "CVE-2026-42506",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42506"
},
{
"name": "CVE-2026-34479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34479"
},
{
"name": "CVE-2026-22796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
},
{
"name": "CVE-2026-26960",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26960"
},
{
"name": "CVE-2026-42040",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42040"
},
{
"name": "CVE-2026-4867",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4867"
},
{
"name": "CVE-2026-2303",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2303"
},
{
"name": "CVE-2024-6763",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-6763"
},
{
"name": "CVE-2026-27903",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27903"
},
{
"name": "CVE-2026-14981",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14981"
},
{
"name": "CVE-2026-39831",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39831"
},
{
"name": "CVE-2026-39828",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39828"
},
{
"name": "CVE-2026-8924",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8924"
},
{
"name": "CVE-2024-45337",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-45337"
},
{
"name": "CVE-2026-14529",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14529"
},
{
"name": "CVE-2026-59875",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59875"
},
{
"name": "CVE-2026-41843",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41843"
},
{
"name": "CVE-2026-54896",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54896"
},
{
"name": "CVE-2026-25680",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25680"
},
{
"name": "CVE-2026-34487",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34487"
},
{
"name": "CVE-2026-39835",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39835"
},
{
"name": "CVE-2026-42578",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42578"
},
{
"name": "CVE-2026-41850",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41850"
},
{
"name": "CVE-2026-4519",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4519"
},
{
"name": "CVE-2026-34197",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34197"
},
{
"name": "CVE-2024-12905",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-12905"
},
{
"name": "CVE-2024-52046",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-52046"
},
{
"name": "CVE-2026-59873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-59873"
},
{
"name": "CVE-2026-24842",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24842"
},
{
"name": "CVE-2025-47935",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-47935"
},
{
"name": "CVE-2026-40198",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40198"
},
{
"name": "CVE-2026-4111",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4111"
},
{
"name": "CVE-2024-38827",
"url": "https://www.cve.org/CVERecord?id=CVE-2024-38827"
},
{
"name": "CVE-2026-41694",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41694"
},
{
"name": "CVE-2026-23950",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23950"
},
{
"name": "CVE-2026-40046",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40046"
},
{
"name": "CVE-2022-22968",
"url": "https://www.cve.org/CVERecord?id=CVE-2022-22968"
},
{
"name": "CVE-2026-16192",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-16192"
},
{
"name": "CVE-2026-2950",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2950"
},
{
"name": "CVE-2026-54500",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54500"
},
{
"name": "CVE-2026-3304",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3304"
},
{
"name": "CVE-2026-40895",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40895"
},
{
"name": "CVE-2018-10237",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-10237"
},
{
"name": "CVE-2026-14515",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14515"
},
{
"name": "CVE-2026-22016",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22016"
},
{
"name": "CVE-2026-22021",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22021"
},
{
"name": "CVE-2026-6100",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6100"
},
{
"name": "CVE-2026-54904",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54904"
},
{
"name": "CVE-2026-22007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22007"
},
{
"name": "CVE-2025-68160",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
},
{
"name": "CVE-2026-13149",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13149"
},
{
"name": "CVE-2026-54897",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54897"
},
{
"name": "CVE-2026-34268",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34268"
},
{
"name": "CVE-2026-41852",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41852"
},
{
"name": "CVE-2021-22569",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-22569"
},
{
"name": "CVE-2026-3520",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3520"
},
{
"name": "CVE-2026-29786",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-29786"
},
{
"name": "CVE-2026-41006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41006"
},
{
"name": "CVE-2026-41711",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41711"
},
{
"name": "CVE-2026-27830",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27830"
},
{
"name": "CVE-2026-44487",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44487"
},
{
"name": "CVE-2026-2482",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2482"
},
{
"name": "CVE-2026-42038",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42038"
},
{
"name": "CVE-2026-49844",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49844"
},
{
"name": "CVE-2026-25854",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25854"
},
{
"name": "CVE-2026-2332",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2332"
},
{
"name": "CVE-2026-41851",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41851"
},
{
"name": "CVE-2026-42039",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42039"
},
{
"name": "CVE-2026-8149",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8149"
},
{
"name": "CVE-2026-6009",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6009"
},
{
"name": "CVE-2026-9358",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9358"
},
{
"name": "CVE-2026-14446",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14446"
},
{
"name": "CVE-2026-42502",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42502"
},
{
"name": "CVE-2020-8908",
"url": "https://www.cve.org/CVERecord?id=CVE-2020-8908"
},
{
"name": "CVE-2026-42245",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42245"
},
{
"name": "CVE-2026-8723",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8723"
},
{
"name": "CVE-2026-40988",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40988"
},
{
"name": "CVE-2026-41841",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41841"
},
{
"name": "CVE-2026-25681",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25681"
},
{
"name": "CVE-2025-69418",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
},
{
"name": "CVE-2026-54903",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54903"
},
{
"name": "CVE-2026-39304",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39304"
},
{
"name": "CVE-2026-49270",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-49270"
},
{
"name": "CVE-2025-15468",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15468"
},
{
"name": "CVE-2026-25639",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25639"
},
{
"name": "CVE-2026-15064",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15064"
},
{
"name": "CVE-2026-42044",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42044"
},
{
"name": "CVE-2026-54900",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54900"
},
{
"name": "CVE-2018-16487",
"url": "https://www.cve.org/CVERecord?id=CVE-2018-16487"
},
{
"name": "CVE-2023-22899",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-22899"
},
{
"name": "CVE-2026-42034",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42034"
},
{
"name": "CVE-2026-8927",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8927"
},
{
"name": "CVE-2026-41846",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41846"
},
{
"name": "CVE-2025-5889",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-5889"
},
{
"name": "CVE-2026-41035",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41035"
},
{
"name": "CVE-2026-40199",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-40199"
},
{
"name": "CVE-2025-27789",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-27789"
},
{
"name": "CVE-2026-46598",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46598"
},
{
"name": "CVE-2026-44024",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44024"
},
{
"name": "CVE-2026-42246",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42246"
},
{
"name": "CVE-2025-66566",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66566"
},
{
"name": "CVE-2025-66168",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66168"
},
{
"name": "CVE-2026-41409",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41409"
},
{
"name": "CVE-2025-11187",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11187"
},
{
"name": "CVE-2026-14980",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-14980"
},
{
"name": "CVE-2026-54898",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54898"
},
{
"name": "CVE-2026-12143",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12143"
},
{
"name": "CVE-2026-44431",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44431"
},
{
"name": "CVE-2026-26996",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-26996"
},
{
"name": "CVE-2026-44486",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44486"
},
{
"name": "CVE-2026-33227",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33227"
},
{
"name": "CVE-2026-42264",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42264"
},
{
"name": "CVE-2026-46597",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-46597"
},
{
"name": "CVE-2026-44161",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44161"
},
{
"name": "CVE-2026-4786",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4786"
},
{
"name": "CVE-2025-64756",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-64756"
},
{
"name": "CVE-2026-34483",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34483"
},
{
"name": "CVE-2026-44496",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44496"
},
{
"name": "CVE-2026-0636",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-0636"
},
{
"name": "CVE-2026-44492",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44492"
},
{
"name": "CVE-2025-48997",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48997"
},
{
"name": "CVE-2026-24880",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24880"
},
{
"name": "CVE-2021-22570",
"url": "https://www.cve.org/CVERecord?id=CVE-2021-22570"
},
{
"name": "CVE-2026-9547",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9547"
},
{
"name": "CVE-2026-41007",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41007"
},
{
"name": "CVE-2026-42037",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42037"
},
{
"name": "CVE-2026-2004",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
},
{
"name": "CVE-2026-42042",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42042"
},
{
"name": "CVE-2025-21502",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-21502"
},
{
"name": "CVE-2026-35554",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-35554"
},
{
"name": "CVE-2025-48387",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-48387"
},
{
"name": "CVE-2026-12590",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12590"
},
{
"name": "CVE-2026-27727",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27727"
},
{
"name": "CVE-2026-34477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34477"
},
{
"name": "CVE-2026-54902",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54902"
},
{
"name": "CVE-2026-44490",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44490"
},
{
"name": "CVE-2026-54592",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54592"
},
{
"name": "CVE-2023-5752",
"url": "https://www.cve.org/CVERecord?id=CVE-2023-5752"
},
{
"name": "CVE-2026-39827",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-39827"
},
{
"name": "CVE-2025-12183",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-12183"
},
{
"name": "CVE-2025-7338",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-7338"
},
{
"name": "CVE-2026-15280",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-15280"
},
{
"name": "CVE-2026-41848",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41848"
},
{
"name": "CVE-2025-14813",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14813"
},
{
"name": "CVE-2026-31802",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-31802"
},
{
"name": "CVE-2025-13465",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13465"
},
{
"name": "CVE-2026-13311",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13311"
},
{
"name": "CVE-2026-41907",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-41907"
},
{
"name": "CVE-2026-44488",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-44488"
},
{
"name": "CVE-2025-59343",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-59343"
},
{
"name": "CVE-2026-34481",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34481"
},
{
"name": "CVE-2026-27904",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-27904"
},
{
"name": "CVE-2026-8286",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8286"
},
{
"name": "CVE-2026-42257",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42257"
},
{
"name": "CVE-2026-42338",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42338"
}
],
"initial_release_date": "2026-07-31T00:00:00",
"last_revision_date": "2026-07-31T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-0958",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-07-31T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Injection de code indirecte \u00e0 distance (XSS)"
},
{
"description": "Injection de requ\u00eates ill\u00e9gitimes par rebond (CSRF)"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Injection SQL (SQLi)"
},
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
},
{
"description": "Falsification de requ\u00eates c\u00f4t\u00e9 serveur (SSRF)"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
},
{
"description": "\u00c9l\u00e9vation de privil\u00e8ges"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits IBM. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une \u00e9l\u00e9vation de privil\u00e8ges et un d\u00e9ni de service \u00e0 distance.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits IBM",
"vendor_advisories": [
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281450",
"url": "https://www.ibm.com/support/pages/node/7281450"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281625",
"url": "https://www.ibm.com/support/pages/node/7281625"
},
{
"published_at": "2026-07-30",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281949",
"url": "https://www.ibm.com/support/pages/node/7281949"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7277692",
"url": "https://www.ibm.com/support/pages/node/7277692"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281628",
"url": "https://www.ibm.com/support/pages/node/7281628"
},
{
"published_at": "2026-07-24",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281135",
"url": "https://www.ibm.com/support/pages/node/7281135"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281375",
"url": "https://www.ibm.com/support/pages/node/7281375"
},
{
"published_at": "2026-07-29",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281743",
"url": "https://www.ibm.com/support/pages/node/7281743"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281373",
"url": "https://www.ibm.com/support/pages/node/7281373"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281388",
"url": "https://www.ibm.com/support/pages/node/7281388"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281721",
"url": "https://www.ibm.com/support/pages/node/7281721"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281369",
"url": "https://www.ibm.com/support/pages/node/7281369"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281648",
"url": "https://www.ibm.com/support/pages/node/7281648"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281374",
"url": "https://www.ibm.com/support/pages/node/7281374"
},
{
"published_at": "2026-07-24",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281136",
"url": "https://www.ibm.com/support/pages/node/7281136"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281641",
"url": "https://www.ibm.com/support/pages/node/7281641"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281631",
"url": "https://www.ibm.com/support/pages/node/7281631"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281371",
"url": "https://www.ibm.com/support/pages/node/7281371"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281633",
"url": "https://www.ibm.com/support/pages/node/7281633"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281438",
"url": "https://www.ibm.com/support/pages/node/7281438"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281370",
"url": "https://www.ibm.com/support/pages/node/7281370"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281565",
"url": "https://www.ibm.com/support/pages/node/7281565"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281368",
"url": "https://www.ibm.com/support/pages/node/7281368"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281350",
"url": "https://www.ibm.com/support/pages/node/7281350"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281651",
"url": "https://www.ibm.com/support/pages/node/7281651"
},
{
"published_at": "2026-07-30",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281950",
"url": "https://www.ibm.com/support/pages/node/7281950"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281567",
"url": "https://www.ibm.com/support/pages/node/7281567"
},
{
"published_at": "2026-07-23",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7280950",
"url": "https://www.ibm.com/support/pages/node/7280950"
},
{
"published_at": "2026-07-27",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281441",
"url": "https://www.ibm.com/support/pages/node/7281441"
},
{
"published_at": "2026-07-28",
"title": "Bulletin de s\u00e9curit\u00e9 IBM 7281649",
"url": "https://www.ibm.com/support/pages/node/7281649"
}
]
}
CERTFR-2026-AVI-0962
Vulnerability from certfr_avis - Published: 2026-08-04 - Updated: 2026-08-04
De multiples vulnérabilités ont été découvertes dans les produits Tenable. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une atteinte à l'intégrité des données et une injection SQL (SQLi).
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Tenable | Enclave Security | Enclave Security sans le correctif de sécurité SC202607.2 | ||
| Tenable | Sensor Proxy | Sensor Proxy versions antérieures à 1.4.2 |
| Title | Publication Time | Tags | ||||||
|---|---|---|---|---|---|---|---|---|
|
||||||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "Enclave Security sans le correctif de s\u00e9curit\u00e9 SC202607.2",
"product": {
"name": "Enclave Security",
"vendor": {
"name": "Tenable",
"scada": false
}
}
},
{
"description": "Sensor Proxy versions ant\u00e9rieures \u00e0 1.4.2",
"product": {
"name": "Sensor Proxy",
"vendor": {
"name": "Tenable",
"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-66199",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-66199"
},
{
"name": "CVE-2026-23479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23479"
},
{
"name": "CVE-2026-6474",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6474"
},
{
"name": "CVE-2026-6472",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6472"
},
{
"name": "CVE-2025-15469",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15469"
},
{
"name": "CVE-2026-6479",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6479"
},
{
"name": "CVE-2026-7261",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7261"
},
{
"name": "CVE-2026-6104",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6104"
},
{
"name": "CVE-2025-69419",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69419"
},
{
"name": "CVE-2026-6735",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6735"
},
{
"name": "CVE-2025-15467",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15467"
},
{
"name": "CVE-2026-18667",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18667"
},
{
"name": "CVE-2026-2006",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2006"
},
{
"name": "CVE-2026-6637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6637"
},
{
"name": "CVE-2026-6473",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6473"
},
{
"name": "CVE-2026-2005",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2005"
},
{
"name": "CVE-2026-22795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
},
{
"name": "CVE-2026-33857",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33857"
},
{
"name": "CVE-2025-69421",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69421"
},
{
"name": "CVE-2026-25589",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25589"
},
{
"name": "CVE-2025-14179",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14179"
},
{
"name": "CVE-2026-6638",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6638"
},
{
"name": "CVE-2026-25588",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25588"
},
{
"name": "CVE-2026-22796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
},
{
"name": "CVE-2026-7568",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7568"
},
{
"name": "CVE-2026-6722",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6722"
},
{
"name": "CVE-2026-23918",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23918"
},
{
"name": "CVE-2026-24072",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-24072"
},
{
"name": "CVE-2026-6478",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6478"
},
{
"name": "CVE-2026-7258",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7258"
},
{
"name": "CVE-2026-23631",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-23631"
},
{
"name": "CVE-2026-64880",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64880"
},
{
"name": "CVE-2026-64877",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64877"
},
{
"name": "CVE-2026-6475",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6475"
},
{
"name": "CVE-2026-25243",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-25243"
},
{
"name": "CVE-2026-64881",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64881"
},
{
"name": "CVE-2025-68160",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
},
{
"name": "CVE-2026-6477",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6477"
},
{
"name": "CVE-2025-69418",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
},
{
"name": "CVE-2025-15468",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15468"
},
{
"name": "CVE-2026-34032",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34032"
},
{
"name": "CVE-2026-34059",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34059"
},
{
"name": "CVE-2026-42371",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42371"
},
{
"name": "CVE-2025-11187",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-11187"
},
{
"name": "CVE-2026-2003",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2003"
},
{
"name": "CVE-2026-7259",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7259"
},
{
"name": "CVE-2025-68121",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68121"
},
{
"name": "CVE-2025-61726",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-61726"
},
{
"name": "CVE-2026-64878",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64878"
},
{
"name": "CVE-2026-7262",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7262"
},
{
"name": "CVE-2026-33523",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-33523"
},
{
"name": "CVE-2026-2004",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-2004"
},
{
"name": "CVE-2026-7263",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7263"
},
{
"name": "CVE-2025-69420",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69420"
},
{
"name": "CVE-2026-64879",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-64879"
}
],
"initial_release_date": "2026-08-04T00:00:00",
"last_revision_date": "2026-08-04T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-0962",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-08-04T00:00:00.000000"
}
],
"risks": [
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Injection SQL (SQLi)"
},
{
"description": "Non sp\u00e9cifi\u00e9 par l\u0027\u00e9diteur"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans les produits Tenable. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, une atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es et une injection SQL (SQLi).",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans les produits Tenable",
"vendor_advisories": [
{
"published_at": "2026-08-03",
"title": "Bulletin de s\u00e9curit\u00e9 Tenable tns-2026-21",
"url": "https://www.tenable.com/security/tns-2026-21"
},
{
"published_at": "2026-07-31",
"title": "Bulletin de s\u00e9curit\u00e9 Tenable tns-2026-20",
"url": "https://www.tenable.com/security/tns-2026-20"
}
]
}
CERTFR-2026-AVI-1351
Vulnerability from certfr_avis - Published: 2026-10-21 - Updated: 2026-10-21
De multiples vulnérabilités ont été découvertes dans Oracle MySQL. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.
Solutions
Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).
| Vendor | Product | Description | ||
|---|---|---|---|---|
| Oracle | MySQL | MySQL Connectors (_Connector/Python) version 26.7.0 | ||
| Oracle | MySQL | MySQL Connectors (_Connector/Net) version 26.7.0 | ||
| Oracle | MySQL | MySQL Enterprise Backup version 26.7.0 | ||
| Oracle | MySQL | MySQL Enterprise Backup version 8.4.0 à 8.4.12 | ||
| Oracle | MySQL | MySQL Enterprise Backup version 9.7.0 à 9.7.3 | ||
| Oracle | MySQL | MySQL Server version 26.7.0 à 26.7.1 | ||
| Oracle | MySQL | MySQL Server version 9.7.0 à 9.7.3 | ||
| Oracle | MySQL | MySQL Connectors (_Connector/J) version 26.7.0 | ||
| Oracle | MySQL | MySQL Cluster version 26.7.0 et version 26.7.1 | ||
| Oracle | MySQL | MySQL Cluster versions 8.0.0 à 8.0.49 | ||
| Oracle | MySQL | MySQL Connectors (_Connector/ODBC) version 26.7.1 | ||
| Oracle | MySQL | MySQL Router version 26.7.0 | ||
| Oracle | MySQL | MySQL Server version 8.4.0 à 8.4.12 | ||
| Oracle | MySQL | MySQL Enterprise Backup version 8.0.0 à 8.0.49 | ||
| Oracle | MySQL | MySQL Cluster version 8.4.0 à 8.4.12 | ||
| Oracle | MySQL | MySQL Cluster version 8.0.0 à 8.0.37 | ||
| Oracle | MySQL | MySQL Cluster version 9.7.0 à 9.7.3 |
| Title | Publication Time | Tags | |||
|---|---|---|---|---|---|
|
|||||
{
"$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
"affected_systems": [
{
"description": "MySQL Connectors (_Connector/Python) version 26.7.0",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Connectors (_Connector/Net) version 26.7.0",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Enterprise Backup version 26.7.0",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Enterprise Backup version 8.4.0 \u00e0 8.4.12",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Enterprise Backup version 9.7.0 \u00e0 9.7.3",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Server version 26.7.0 \u00e0 26.7.1",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Server version 9.7.0 \u00e0 9.7.3",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Connectors (_Connector/J) version 26.7.0",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Cluster version 26.7.0 et version 26.7.1",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Cluster versions 8.0.0 \u00e0 8.0.49",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Connectors (_Connector/ODBC) version 26.7.1",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Router version 26.7.0",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Server version 8.4.0 \u00e0 8.4.12",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Enterprise Backup version 8.0.0 \u00e0 8.0.49",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Cluster version 8.4.0 \u00e0 8.4.12",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Cluster version 8.0.0 \u00e0 8.0.37",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
},
{
"description": "MySQL Cluster version 9.7.0 \u00e0 9.7.3",
"product": {
"name": "MySQL",
"vendor": {
"name": "Oracle",
"scada": false
}
}
}
],
"affected_systems_content": "",
"content": "## Solutions\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des correctifs (cf. section Documentation).",
"cves": [
{
"name": "CVE-2026-101721",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101721"
},
{
"name": "CVE-2026-101632",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101632"
},
{
"name": "CVE-2026-101629",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101629"
},
{
"name": "CVE-2026-101611",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101611"
},
{
"name": "CVE-2026-101731",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101731"
},
{
"name": "CVE-2025-10148",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-10148"
},
{
"name": "CVE-2026-34180",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34180"
},
{
"name": "CVE-2026-83404",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-83404"
},
{
"name": "CVE-2026-101618",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101618"
},
{
"name": "CVE-2026-42766",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42766"
},
{
"name": "CVE-2026-9076",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9076"
},
{
"name": "CVE-2026-13608",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-13608"
},
{
"name": "CVE-2026-101720",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101720"
},
{
"name": "CVE-2026-1965",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-1965"
},
{
"name": "CVE-2026-101798",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101798"
},
{
"name": "CVE-2026-101624",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101624"
},
{
"name": "CVE-2026-42770",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42770"
},
{
"name": "CVE-2026-101770",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101770"
},
{
"name": "CVE-2026-8926",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8926"
},
{
"name": "CVE-2026-101776",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101776"
},
{
"name": "CVE-2025-69419",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69419"
},
{
"name": "CVE-2026-3783",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3783"
},
{
"name": "CVE-2026-63074",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63074"
},
{
"name": "CVE-2026-8458",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8458"
},
{
"name": "CVE-2026-6429",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6429"
},
{
"name": "CVE-2026-101617",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101617"
},
{
"name": "CVE-2026-45445",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45445"
},
{
"name": "CVE-2025-15467",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15467"
},
{
"name": "CVE-2026-101752",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101752"
},
{
"name": "CVE-2026-101785",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101785"
},
{
"name": "CVE-2026-101726",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101726"
},
{
"name": "CVE-2026-101608",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101608"
},
{
"name": "CVE-2026-101800",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101800"
},
{
"name": "CVE-2026-101628",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101628"
},
{
"name": "CVE-2026-101732",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101732"
},
{
"name": "CVE-2026-7383",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7383"
},
{
"name": "CVE-2026-22795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22795"
},
{
"name": "CVE-2026-101769",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101769"
},
{
"name": "CVE-2026-101724",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101724"
},
{
"name": "CVE-2026-10536",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-10536"
},
{
"name": "CVE-2026-101677",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101677"
},
{
"name": "CVE-2026-8932",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8932"
},
{
"name": "CVE-2026-101747",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101747"
},
{
"name": "CVE-2026-28389",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28389"
},
{
"name": "CVE-2025-10966",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-10966"
},
{
"name": "CVE-2026-101607",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101607"
},
{
"name": "CVE-2026-101804",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101804"
},
{
"name": "CVE-2026-101762",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101762"
},
{
"name": "CVE-2026-101756",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101756"
},
{
"name": "CVE-2026-101786",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101786"
},
{
"name": "CVE-2026-101754",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101754"
},
{
"name": "CVE-2026-11856",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-11856"
},
{
"name": "CVE-2026-101783",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101783"
},
{
"name": "CVE-2025-69421",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69421"
},
{
"name": "CVE-2026-101803",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101803"
},
{
"name": "CVE-2026-101722",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101722"
},
{
"name": "CVE-2026-101797",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101797"
},
{
"name": "CVE-2026-101772",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101772"
},
{
"name": "CVE-2026-101768",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101768"
},
{
"name": "CVE-2026-101627",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101627"
},
{
"name": "CVE-2026-101778",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101778"
},
{
"name": "CVE-2026-6253",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6253"
},
{
"name": "CVE-2026-12064",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-12064"
},
{
"name": "CVE-2026-101771",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101771"
},
{
"name": "CVE-2026-101633",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101633"
},
{
"name": "CVE-2026-101806",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101806"
},
{
"name": "CVE-2026-101789",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101789"
},
{
"name": "CVE-2026-22796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-22796"
},
{
"name": "CVE-2026-101609",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101609"
},
{
"name": "CVE-2026-101631",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101631"
},
{
"name": "CVE-2025-9232",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9232"
},
{
"name": "CVE-2026-101796",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101796"
},
{
"name": "CVE-2026-45447",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45447"
},
{
"name": "CVE-2026-8924",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8924"
},
{
"name": "CVE-2026-101733",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101733"
},
{
"name": "CVE-2025-14017",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14017"
},
{
"name": "CVE-2026-3805",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3805"
},
{
"name": "CVE-2026-101773",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101773"
},
{
"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-2026-28387",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28387"
},
{
"name": "CVE-2026-101637",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101637"
},
{
"name": "CVE-2026-28388",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28388"
},
{
"name": "CVE-2026-101755",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101755"
},
{
"name": "CVE-2026-101725",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101725"
},
{
"name": "CVE-2026-101761",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101761"
},
{
"name": "CVE-2026-101623",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101623"
},
{
"name": "CVE-2026-101621",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101621"
},
{
"name": "CVE-2026-101613",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101613"
},
{
"name": "CVE-2026-101753",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101753"
},
{
"name": "CVE-2026-18924",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-18924"
},
{
"name": "CVE-2026-45446",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-45446"
},
{
"name": "CVE-2026-101787",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101787"
},
{
"name": "CVE-2026-9080",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9080"
},
{
"name": "CVE-2026-63076",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63076"
},
{
"name": "CVE-2026-101784",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101784"
},
{
"name": "CVE-2026-101781",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101781"
},
{
"name": "CVE-2026-101779",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101779"
},
{
"name": "CVE-2025-68160",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-68160"
},
{
"name": "CVE-2026-9545",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9545"
},
{
"name": "CVE-2026-101810",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101810"
},
{
"name": "CVE-2026-101728",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101728"
},
{
"name": "CVE-2025-13034",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-13034"
},
{
"name": "CVE-2025-9086",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9086"
},
{
"name": "CVE-2026-101799",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101799"
},
{
"name": "CVE-2026-101612",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101612"
},
{
"name": "CVE-2026-101610",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101610"
},
{
"name": "CVE-2026-28390",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-28390"
},
{
"name": "CVE-2025-14524",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14524"
},
{
"name": "CVE-2026-42767",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-42767"
},
{
"name": "CVE-2026-101775",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101775"
},
{
"name": "CVE-2026-101743",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101743"
},
{
"name": "CVE-2026-4873",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-4873"
},
{
"name": "CVE-2025-69418",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69418"
},
{
"name": "CVE-2026-101729",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101729"
},
{
"name": "CVE-2026-101750",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101750"
},
{
"name": "CVE-2026-75803",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-75803"
},
{
"name": "CVE-2026-5773",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5773"
},
{
"name": "CVE-2026-8927",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8927"
},
{
"name": "CVE-2026-101619",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101619"
},
{
"name": "CVE-2026-101620",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101620"
},
{
"name": "CVE-2026-6276",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-6276"
},
{
"name": "CVE-2025-9230",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-9230"
},
{
"name": "CVE-2026-101625",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101625"
},
{
"name": "CVE-2026-101748",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101748"
},
{
"name": "CVE-2025-15079",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15079"
},
{
"name": "CVE-2026-101679",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101679"
},
{
"name": "CVE-2026-101788",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101788"
},
{
"name": "CVE-2026-101795",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101795"
},
{
"name": "CVE-2026-101777",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101777"
},
{
"name": "CVE-2026-101614",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101614"
},
{
"name": "CVE-2026-101615",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101615"
},
{
"name": "CVE-2026-101626",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101626"
},
{
"name": "CVE-2025-14819",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-14819"
},
{
"name": "CVE-2026-34182",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-34182"
},
{
"name": "CVE-2026-101616",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101616"
},
{
"name": "CVE-2026-101766",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101766"
},
{
"name": "CVE-2026-101513",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101513"
},
{
"name": "CVE-2026-9547",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-9547"
},
{
"name": "CVE-2026-101622",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101622"
},
{
"name": "CVE-2026-54874",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-54874"
},
{
"name": "CVE-2026-101749",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101749"
},
{
"name": "CVE-2026-101774",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101774"
},
{
"name": "CVE-2026-101678",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101678"
},
{
"name": "CVE-2026-101751",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101751"
},
{
"name": "CVE-2026-7168",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-7168"
},
{
"name": "CVE-2026-101801",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101801"
},
{
"name": "CVE-2026-101802",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101802"
},
{
"name": "CVE-2026-101727",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101727"
},
{
"name": "CVE-2026-101760",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101760"
},
{
"name": "CVE-2026-101730",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101730"
},
{
"name": "CVE-2025-69420",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-69420"
},
{
"name": "CVE-2026-101780",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101780"
},
{
"name": "CVE-2025-15224",
"url": "https://www.cve.org/CVERecord?id=CVE-2025-15224"
},
{
"name": "CVE-2026-8286",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-8286"
},
{
"name": "CVE-2026-31790",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-31790"
},
{
"name": "CVE-2026-63072",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-63072"
},
{
"name": "CVE-2026-5545",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-5545"
},
{
"name": "CVE-2026-101794",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-101794"
},
{
"name": "CVE-2026-3784",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-3784"
}
],
"initial_release_date": "2026-10-21T00:00:00",
"last_revision_date": "2026-10-21T00:00:00",
"links": [],
"reference": "CERTFR-2026-AVI-1351",
"revisions": [
{
"description": "Version initiale",
"revision_date": "2026-10-21T00:00:00.000000"
}
],
"risks": [
{
"description": "D\u00e9ni de service \u00e0 distance"
},
{
"description": "Ex\u00e9cution de code arbitraire \u00e0 distance"
},
{
"description": "Atteinte \u00e0 l\u0027int\u00e9grit\u00e9 des donn\u00e9es"
},
{
"description": "Contournement de la politique de s\u00e9curit\u00e9"
},
{
"description": "Atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es"
}
],
"summary": "De multiples vuln\u00e9rabilit\u00e9s ont \u00e9t\u00e9 d\u00e9couvertes dans Oracle MySQL. Certaines d\u0027entre elles permettent \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire \u00e0 distance, un d\u00e9ni de service \u00e0 distance et une atteinte \u00e0 la confidentialit\u00e9 des donn\u00e9es.",
"title": "Multiples vuln\u00e9rabilit\u00e9s dans Oracle MySQL",
"vendor_advisories": [
{
"published_at": "2026-10-20",
"title": "Bulletin de s\u00e9curit\u00e9 Oracle MySQL cpuoct2026",
"url": "https://www.oracle.com/security-alerts/cpuoct2026.html"
}
]
}
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 |
| Title | Publication Time | Tags | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
{
"$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-JU79609 (CVE-2026-22795)
Vulnerability from cleanstart – Published: 2026-09-29 00:39 – Updated: 2026-10-08 15:18 – Source websiteSecurity vulnerability affects the apache-superset package. Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
{
"affected": [
{
"package": {
"ecosystem": "CleanStart",
"name": "apache-superset",
"purl": "pkg:apk/cleanstart/apache-superset"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "5.0.0-r10"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"credits": [],
"database_specific": {},
"details": "Security vulnerability affects the apache-superset package. Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.",
"id": "CLEANSTART-2026-JU79609",
"modified": "2026-10-08T15:18:04Z",
"published": "2026-09-29T00:39:28.447411Z",
"references": [
{
"type": "ADVISORY",
"url": "https://github.com/cleanstart-dev/cleanstart-security-advisories/tree/main/advisories/2026/CLEANSTART-2026-JU79609.json"
},
{
"type": "WEB",
"url": "https://osv.dev/vulnerability/CVE-2026-22795"
},
{
"type": "WEB",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22795"
}
],
"related": [],
"schema_version": "1.7.3",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "Issue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file",
"upstream": [
"CVE-2026-22795"
]
}
OESA-2026-1411 (CVE-2025-15467)
Vulnerability from osv_openeuler – Published: 2026-02-13 11:10 – Updated: 2026-08-06 11:10 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: Parsing CMS AuthEnvelopedData message with maliciously crafted AEAD parameters can trigger a stack buffer overflow.
Impact summary: A stack buffer overflow may lead to a crash, causing Denial of Service, or potentially remote code execution.
When parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as AES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is copied into a fixed-size stack buffer without verifying that its length fits the destination. An attacker can supply a crafted CMS message with an oversized IV, causing a stack-based out-of-bounds write before any authentication or tag verification occurs.
Applications and services that parse untrusted CMS or PKCS#7 content using AEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable. Because the overflow occurs prior to authentication, no valid key material is required to trigger it. While exploitability to remote code execution depends on platform and toolchain mitigations, the stack-based write primitive represents a severe risk.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the CMS implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.
OpenSSL 1.1.1 and 1.0.2 are not affected by this issue.(CVE-2025-15467)
Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.
The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.۴, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)
| URL | Type | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-3.0.12-24.oe2403sp2.aarch64.rpm",
"openssl-debuginfo-3.0.12-24.oe2403sp2.aarch64.rpm",
"openssl-debugsource-3.0.12-24.oe2403sp2.aarch64.rpm",
"openssl-devel-3.0.12-24.oe2403sp2.aarch64.rpm",
"openssl-libs-3.0.12-24.oe2403sp2.aarch64.rpm",
"openssl-perl-3.0.12-24.oe2403sp2.aarch64.rpm"
],
"noarch": [
"openssl-help-3.0.12-24.oe2403sp2.noarch.rpm"
],
"src": [
"openssl-3.0.12-24.oe2403sp2.src.rpm"
],
"x86_64": [
"openssl-3.0.12-24.oe2403sp2.x86_64.rpm",
"openssl-debuginfo-3.0.12-24.oe2403sp2.x86_64.rpm",
"openssl-debugsource-3.0.12-24.oe2403sp2.x86_64.rpm",
"openssl-devel-3.0.12-24.oe2403sp2.x86_64.rpm",
"openssl-libs-3.0.12-24.oe2403sp2.x86_64.rpm",
"openssl-perl-3.0.12-24.oe2403sp2.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP2",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-24.03-LTS-SP2"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.12-24.oe2403sp2"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "Critical"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: Parsing CMS AuthEnvelopedData message with maliciously\ncrafted AEAD parameters can trigger a stack buffer overflow.\n\nImpact summary: A stack buffer overflow may lead to a crash, causing Denial\nof Service, or potentially remote code execution.\n\nWhen parsing CMS AuthEnvelopedData structures that use AEAD ciphers such as\nAES-GCM, the IV (Initialization Vector) encoded in the ASN.1 parameters is\ncopied into a fixed-size stack buffer without verifying that its length fits\nthe destination. An attacker can supply a crafted CMS message with an\noversized IV, causing a stack-based out-of-bounds write before any\nauthentication or tag verification occurs.\n\nApplications and services that parse untrusted CMS or PKCS#7 content using\nAEAD ciphers (e.g., S/MIME AuthEnvelopedData with AES-GCM) are vulnerable.\nBecause the overflow occurs prior to authentication, no valid key material\nis required to trigger it. While exploitability to remote code execution\ndepends on platform and toolchain mitigations, the stack-based write\nprimitive represents a severe risk.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this\nissue, as the CMS implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3 and 3.0 are vulnerable to this issue.\n\nOpenSSL 1.1.1 and 1.0.2 are not affected by this issue.(CVE-2025-15467)\n\nIssue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.\n\nImpact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.\n\nThe low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.\n\nHowever, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.\n\nOpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)\n\nIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.\n\nImpact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.\n\nThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.\n\nThe vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.\u06f4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)\n\nIssue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.\n\nImpact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.\n\nThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)\n\nIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\ndereference in the PKCS12_item_decrypt_d2i_ex() function.\n\nImpact summary: A NULL pointer dereference can trigger a crash which leads to\nDenial of Service for an application processing PKCS#12 files.\n\nThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\nparameter is NULL before dereferencing it. When called from\nPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\nbe NULL, causing a crash. The vulnerability is limited to Denial of Service\nand cannot be escalated to achieve code execution or memory disclosure.\n\nExploiting this issue requires an attacker to provide a malformed PKCS#12 file\nto an application that processes it. For that reason the issue was assessed as\nLow severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)\n\nIssue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)\n\nIssue summary: A type confusion vulnerability exists in the signature\nverification of signed PKCS#7 data where an ASN1_TYPE union member is\naccessed without first validating the type, causing an invalid or NULL\npointer dereference when processing malformed PKCS#7 data.\n\nImpact summary: An application performing signature verification of PKCS#7\ndata or calling directly the PKCS7_digest_from_attributes() function can be\ncaused to dereference an invalid or NULL pointer when reading, resulting in\na Denial of Service.\n\nThe function PKCS7_digest_from_attributes() accesses the message digest attribute\nvalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\nthis results in accessing invalid memory through the ASN1_TYPE union, causing\na crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed\nsigned PKCS#7 to an application that verifies it. The impact of the\nexploit is just a Denial of Service, the PKCS7 API is legacy and applications\nshould be using the CMS API instead. For these reasons the issue was\nassessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)",
"id": "OESA-2026-1411",
"modified": "2026-08-06T11:10:25Z",
"published": "2026-02-13T11:10:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1411"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-15467"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69418"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69419"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69420"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69421"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22795"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22796"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2025-15467",
"CVE-2025-69418",
"CVE-2025-69419",
"CVE-2025-69420",
"CVE-2025-69421",
"CVE-2026-22795",
"CVE-2026-22796"
]
}
OESA-2026-1412 (CVE-2025-69418)
Vulnerability from osv_openeuler – Published: 2026-02-13 11:10 – Updated: 2026-08-06 11:10 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.
The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.۴, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)
| URL | Type | ||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
|||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-3.0.12-33.oe2403sp3.aarch64.rpm",
"openssl-debuginfo-3.0.12-33.oe2403sp3.aarch64.rpm",
"openssl-debugsource-3.0.12-33.oe2403sp3.aarch64.rpm",
"openssl-devel-3.0.12-33.oe2403sp3.aarch64.rpm",
"openssl-libs-3.0.12-33.oe2403sp3.aarch64.rpm",
"openssl-perl-3.0.12-33.oe2403sp3.aarch64.rpm"
],
"noarch": [
"openssl-help-3.0.12-33.oe2403sp3.noarch.rpm"
],
"src": [
"openssl-3.0.12-33.oe2403sp3.src.rpm"
],
"x86_64": [
"openssl-3.0.12-33.oe2403sp3.x86_64.rpm",
"openssl-debuginfo-3.0.12-33.oe2403sp3.x86_64.rpm",
"openssl-debugsource-3.0.12-33.oe2403sp3.x86_64.rpm",
"openssl-devel-3.0.12-33.oe2403sp3.x86_64.rpm",
"openssl-libs-3.0.12-33.oe2403sp3.x86_64.rpm",
"openssl-perl-3.0.12-33.oe2403sp3.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:24.03-LTS-SP3",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-24.03-LTS-SP3"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "3.0.12-33.oe2403sp3"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.\n\nImpact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.\n\nThe low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.\n\nHowever, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.\n\nOpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)\n\nIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.\n\nImpact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.\n\nThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.\n\nThe vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.\u06f4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)\n\nIssue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.\n\nImpact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.\n\nThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)\n\nIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\ndereference in the PKCS12_item_decrypt_d2i_ex() function.\n\nImpact summary: A NULL pointer dereference can trigger a crash which leads to\nDenial of Service for an application processing PKCS#12 files.\n\nThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\nparameter is NULL before dereferencing it. When called from\nPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\nbe NULL, causing a crash. The vulnerability is limited to Denial of Service\nand cannot be escalated to achieve code execution or memory disclosure.\n\nExploiting this issue requires an attacker to provide a malformed PKCS#12 file\nto an application that processes it. For that reason the issue was assessed as\nLow severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)\n\nIssue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)\n\nIssue summary: A type confusion vulnerability exists in the signature\nverification of signed PKCS#7 data where an ASN1_TYPE union member is\naccessed without first validating the type, causing an invalid or NULL\npointer dereference when processing malformed PKCS#7 data.\n\nImpact summary: An application performing signature verification of PKCS#7\ndata or calling directly the PKCS7_digest_from_attributes() function can be\ncaused to dereference an invalid or NULL pointer when reading, resulting in\na Denial of Service.\n\nThe function PKCS7_digest_from_attributes() accesses the message digest attribute\nvalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\nthis results in accessing invalid memory through the ASN1_TYPE union, causing\na crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed\nsigned PKCS#7 to an application that verifies it. The impact of the\nexploit is just a Denial of Service, the PKCS7 API is legacy and applications\nshould be using the CMS API instead. For these reasons the issue was\nassessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)",
"id": "OESA-2026-1412",
"modified": "2026-08-06T11:10:25Z",
"published": "2026-02-13T11:10:25Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1412"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69418"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69419"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69420"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69421"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22795"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22796"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2025-69418",
"CVE-2025-69419",
"CVE-2025-69420",
"CVE-2025-69421",
"CVE-2026-22795",
"CVE-2026-22796"
]
}
OESA-2026-1413 (CVE-2025-68160)
Vulnerability from osv_openeuler – Published: 2026-02-13 11:10 – Updated: 2026-08-06 11:10 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-68160)
Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.
The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.۴, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)
| URL | Type | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-1.1.1f-41.oe2003sp4.aarch64.rpm",
"openssl-debuginfo-1.1.1f-41.oe2003sp4.aarch64.rpm",
"openssl-debugsource-1.1.1f-41.oe2003sp4.aarch64.rpm",
"openssl-devel-1.1.1f-41.oe2003sp4.aarch64.rpm",
"openssl-libs-1.1.1f-41.oe2003sp4.aarch64.rpm"
],
"noarch": [
"openssl-help-1.1.1f-41.oe2003sp4.noarch.rpm"
],
"src": [
"openssl-1.1.1f-41.oe2003sp4.src.rpm"
],
"x86_64": [
"openssl-1.1.1f-41.oe2003sp4.x86_64.rpm",
"openssl-debuginfo-1.1.1f-41.oe2003sp4.x86_64.rpm",
"openssl-debugsource-1.1.1f-41.oe2003sp4.x86_64.rpm",
"openssl-devel-1.1.1f-41.oe2003sp4.x86_64.rpm",
"openssl-libs-1.1.1f-41.oe2003sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:20.03-LTS-SP4",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-20.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1f-41.oe2003sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: Writing large, newline-free data into a BIO chain using the\nline-buffering filter where the next BIO performs short writes can trigger\na heap-based out-of-bounds write.\n\nImpact summary: This out-of-bounds write can cause memory corruption which\ntypically results in a crash, leading to Denial of Service for an application.\n\nThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\nTLS/SSL data paths. In OpenSSL command-line applications, it is typically\nonly pushed onto stdout/stderr on VMS systems. Third-party applications that\nexplicitly use this filter with a BIO chain that can short-write and that\nwrite large, newline-free data influenced by an attacker would be affected.\nHowever, the circumstances where this could happen are unlikely to be under\nattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\ndata controlled by an attacker. For that reason the issue was assessed as\nLow severity.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the BIO implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-68160)\n\nIssue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.\n\nImpact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.\n\nThe low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.\n\nHowever, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.\n\nOpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)\n\nIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.\n\nImpact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.\n\nThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.\n\nThe vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.\u06f4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)\n\nIssue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.\n\nImpact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.\n\nThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)\n\nIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\ndereference in the PKCS12_item_decrypt_d2i_ex() function.\n\nImpact summary: A NULL pointer dereference can trigger a crash which leads to\nDenial of Service for an application processing PKCS#12 files.\n\nThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\nparameter is NULL before dereferencing it. When called from\nPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\nbe NULL, causing a crash. The vulnerability is limited to Denial of Service\nand cannot be escalated to achieve code execution or memory disclosure.\n\nExploiting this issue requires an attacker to provide a malformed PKCS#12 file\nto an application that processes it. For that reason the issue was assessed as\nLow severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)\n\nIssue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)\n\nIssue summary: A type confusion vulnerability exists in the signature\nverification of signed PKCS#7 data where an ASN1_TYPE union member is\naccessed without first validating the type, causing an invalid or NULL\npointer dereference when processing malformed PKCS#7 data.\n\nImpact summary: An application performing signature verification of PKCS#7\ndata or calling directly the PKCS7_digest_from_attributes() function can be\ncaused to dereference an invalid or NULL pointer when reading, resulting in\na Denial of Service.\n\nThe function PKCS7_digest_from_attributes() accesses the message digest attribute\nvalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\nthis results in accessing invalid memory through the ASN1_TYPE union, causing\na crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed\nsigned PKCS#7 to an application that verifies it. The impact of the\nexploit is just a Denial of Service, the PKCS7 API is legacy and applications\nshould be using the CMS API instead. For these reasons the issue was\nassessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)",
"id": "OESA-2026-1413",
"modified": "2026-08-06T11:10:26Z",
"published": "2026-02-13T11:10:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1413"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68160"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69418"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69419"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69420"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69421"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22795"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22796"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2025-68160",
"CVE-2025-69418",
"CVE-2025-69419",
"CVE-2025-69420",
"CVE-2025-69421",
"CVE-2026-22795",
"CVE-2026-22796"
]
}
OESA-2026-1414 (CVE-2025-68160)
Vulnerability from osv_openeuler – Published: 2026-02-13 11:10 – Updated: 2026-08-06 11:10 – Source websiteOpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.
Security Fix(es):
Issue summary: Writing large, newline-free data into a BIO chain using the line-buffering filter where the next BIO performs short writes can trigger a heap-based out-of-bounds write.
Impact summary: This out-of-bounds write can cause memory corruption which typically results in a crash, leading to Denial of Service for an application.
The line-buffering BIO filter (BIO_f_linebuffer) is not used by default in TLS/SSL data paths. In OpenSSL command-line applications, it is typically only pushed onto stdout/stderr on VMS systems. Third-party applications that explicitly use this filter with a BIO chain that can short-write and that write large, newline-free data influenced by an attacker would be affected. However, the circumstances where this could happen are unlikely to be under attacker control, and BIO_f_linebuffer is unlikely to be handling non-curated data controlled by an attacker. For that reason the issue was assessed as Low severity.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the BIO implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-68160)
Issue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.
Impact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.
The low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.
However, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.
OpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)
Issue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.
Impact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.
The OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.
The vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.۴, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)
Issue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.
Impact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)
Issue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer dereference in the PKCS12_item_decrypt_d2i_ex() function.
Impact summary: A NULL pointer dereference can trigger a crash which leads to Denial of Service for an application processing PKCS#12 files.
The PKCS12_item_decrypt_d2i_ex() function does not check whether the oct parameter is NULL before dereferencing it. When called from PKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can be NULL, causing a crash. The vulnerability is limited to Denial of Service and cannot be escalated to achieve code execution or memory disclosure.
Exploiting this issue requires an attacker to provide a malformed PKCS#12 file to an application that processes it. For that reason the issue was assessed as Low severity according to our Security Policy.
The FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)
Issue summary: An invalid or NULL pointer dereference can happen in an application processing a malformed PKCS#12 file.
Impact summary: An application processing a malformed PKCS#12 file can be caused to dereference an invalid or NULL pointer on memory read, resulting in a Denial of Service.
A type confusion vulnerability exists in PKCS#12 parsing code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid pointer read.
The location is constrained to a 1-byte address space, meaning any attempted pointer manipulation can only target addresses between 0x00 and 0xFF. This range corresponds to the zero page, which is unmapped on most modern operating systems and will reliably result in a crash, leading only to a Denial of Service. Exploiting this issue also requires a user or application to process a maliciously crafted PKCS#12 file. It is uncommon to accept untrusted PKCS#12 files in applications as they are usually used to store private keys which are trusted by definition. For these reasons, the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS12 implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.
OpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)
Issue summary: A type confusion vulnerability exists in the signature verification of signed PKCS#7 data where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing malformed PKCS#7 data.
Impact summary: An application performing signature verification of PKCS#7 data or calling directly the PKCS7_digest_from_attributes() function can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.
The function PKCS7_digest_from_attributes() accesses the message digest attribute value without validating its type. When the type is not V_ASN1_OCTET_STRING, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.
Exploiting this vulnerability requires an attacker to provide a malformed signed PKCS#7 to an application that verifies it. The impact of the exploit is just a Denial of Service, the PKCS7 API is legacy and applications should be using the CMS API instead. For these reasons the issue was assessed as Low severity.
The FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#7 parsing implementation is outside the OpenSSL FIPS module boundary.
OpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)
| URL | Type | |||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
||||||||||||||||||||||||||
{
"affected": [
{
"ecosystem_specific": {
"aarch64": [
"openssl-1.1.1wa-15.oe2203sp4.aarch64.rpm",
"openssl-debuginfo-1.1.1wa-15.oe2203sp4.aarch64.rpm",
"openssl-debugsource-1.1.1wa-15.oe2203sp4.aarch64.rpm",
"openssl-devel-1.1.1wa-15.oe2203sp4.aarch64.rpm",
"openssl-libs-1.1.1wa-15.oe2203sp4.aarch64.rpm",
"openssl-perl-1.1.1wa-15.oe2203sp4.aarch64.rpm"
],
"noarch": [
"openssl-help-1.1.1wa-15.oe2203sp4.noarch.rpm"
],
"src": [
"openssl-1.1.1wa-15.oe2203sp4.src.rpm"
],
"x86_64": [
"openssl-1.1.1wa-15.oe2203sp4.x86_64.rpm",
"openssl-debuginfo-1.1.1wa-15.oe2203sp4.x86_64.rpm",
"openssl-debugsource-1.1.1wa-15.oe2203sp4.x86_64.rpm",
"openssl-devel-1.1.1wa-15.oe2203sp4.x86_64.rpm",
"openssl-libs-1.1.1wa-15.oe2203sp4.x86_64.rpm",
"openssl-perl-1.1.1wa-15.oe2203sp4.x86_64.rpm"
]
},
"package": {
"ecosystem": "openEuler:22.03-LTS-SP4",
"name": "openssl",
"purl": "pkg:rpm/openEuler/openssl\u0026distro=openEuler-22.03-LTS-SP4"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1.1.1wa-15.oe2203sp4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"database_specific": {
"severity": "High"
},
"details": "OpenSSL is a robust, commercial-grade, and full-featured toolkit for the Transport Layer Security (TLS) and Secure Sockets Layer (SSL) protocols.\r\n\r\nSecurity Fix(es):\n\nIssue summary: Writing large, newline-free data into a BIO chain using the\nline-buffering filter where the next BIO performs short writes can trigger\na heap-based out-of-bounds write.\n\nImpact summary: This out-of-bounds write can cause memory corruption which\ntypically results in a crash, leading to Denial of Service for an application.\n\nThe line-buffering BIO filter (BIO_f_linebuffer) is not used by default in\nTLS/SSL data paths. In OpenSSL command-line applications, it is typically\nonly pushed onto stdout/stderr on VMS systems. Third-party applications that\nexplicitly use this filter with a BIO chain that can short-write and that\nwrite large, newline-free data influenced by an attacker would be affected.\nHowever, the circumstances where this could happen are unlikely to be under\nattacker control, and BIO_f_linebuffer is unlikely to be handling non-curated\ndata controlled by an attacker. For that reason the issue was assessed as\nLow severity.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the BIO implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-68160)\n\nIssue summary: When using the low-level OCB API directly with AES-NI or other hardware-accelerated code paths, inputs whose length is not a multiple of 16 bytes can leave the final partial block unencrypted and unauthenticated.\n\nImpact summary: The trailing 1-15 bytes of a message may be exposed in cleartext on encryption and are not covered by the authentication tag, allowing an attacker to read or tamper with those bytes without detection.\n\nThe low-level OCB encrypt and decrypt routines in the hardware-accelerated stream path process full 16-byte blocks but do not advance the input/output pointers. The subsequent tail-handling code then operates on the original base pointers, effectively reprocessing the beginning of the buffer while leaving the actual trailing bytes unprocessed. The authentication checksum also excludes the true tail bytes.\n\nHowever, typical OpenSSL consumers using EVP are not affected because the higher-level EVP and provider OCB implementations split inputs so that full blocks and trailing partial blocks are processed in separate calls, avoiding the problematic code path. Additionally, TLS does not use OCB ciphersuites. The vulnerability only affects applications that call the low-level CRYPTO_ocb128_encrypt() or CRYPTO_ocb128_decrypt() functions directly with non-block-aligned lengths in a single call on hardware-accelerated builds. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3six, 3five, 3four, 3three, 3two, 3one and 3zero are not affected by this issue, as OCB mode is not a FIPS-approved algorithm.\n\nOpenSSL 3six, 3five, 3four, 3three, 3zero and 1one1 are vulnerable to this issue. OpenSSL 1zero2 is not affected by this issue.(CVE-2025-69418)\n\nIssue summary: Calling PKCS12_get_friendlyname() function on a maliciously crafted PKCS#12 file with a BMPString (UTF-16BE) friendly name containing non-ASCII BMP code point can trigger a one byte write before the allocated buffer.\n\nImpact summary: The out-of-bounds write can cause a memory corruption which can have various consequences including a Denial of Service.\n\nThe OPENSSL_uni2utf8() function performs a two-pass conversion of a PKCS#12 BMPString (UTF-16BE) to UTF-8. In the second pass, when emitting UTF-8 bytes, the helper function bmp_to_utf8() incorrectly forwards the remaining UTF-16 source byte count as the destination buffer capacity to UTF8_putc(). For BMP code points above U+07FF, UTF-8 requires three bytes, but the forwarded capacity can be just two bytes. UTF8_putc() then returns -1, and this negative value is added to the output length without validation, causing the length to become negative. The subsequent trailing NUL byte is then written at a negative offset, causing write outside of heap allocated buffer.\n\nThe vulnerability is reachable via the public PKCS12_get_friendlyname() API when parsing attacker-controlled PKCS#12 files. While PKCS12_parse() uses a different code path that avoids this issue, PKCS12_get_friendlyname() directly invokes the vulnerable function. Exploitation requires an attacker to provide a malicious PKCS#12 file to be parsed by the application and the attacker can just trigger a one zero byte write before the allocated buffer. For that reason the issue was assessed as Low severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.\u06f4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69419)\n\nIssue summary: A type confusion vulnerability exists in the TimeStamp Response verification code where an ASN1_TYPE union member is accessed without first validating the type, causing an invalid or NULL pointer dereference when processing a malformed TimeStamp Response file.\n\nImpact summary: An application calling TS_RESP_verify_response() with a malformed TimeStamp Response can be caused to dereference an invalid or NULL pointer when reading, resulting in a Denial of Service.\n\nThe functions ossl_ess_get_signing_cert() and ossl_ess_get_signing_cert_v2() access the signing cert attribute value without validating its type. When the type is not V_ASN1_SEQUENCE, this results in accessing invalid memory through the ASN1_TYPE union, causing a crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed TimeStamp Response to an application that verifies timestamp responses. The TimeStamp protocol (RFC 3161) is not widely used and the impact of the exploit is just a Denial of Service. For these reasons the issue was assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue, as the TimeStamp Response implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, series3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2025-69420)\n\nIssue summary: Processing a malformed PKCS#12 file can trigger a NULL pointer\ndereference in the PKCS12_item_decrypt_d2i_ex() function.\n\nImpact summary: A NULL pointer dereference can trigger a crash which leads to\nDenial of Service for an application processing PKCS#12 files.\n\nThe PKCS12_item_decrypt_d2i_ex() function does not check whether the oct\nparameter is NULL before dereferencing it. When called from\nPKCS12_unpack_p7encdata() with a malformed PKCS#12 file, this parameter can\nbe NULL, causing a crash. The vulnerability is limited to Denial of Service\nand cannot be escalated to achieve code execution or memory disclosure.\n\nExploiting this issue requires an attacker to provide a malformed PKCS#12 file\nto an application that processes it. For that reason the issue was assessed as\nLow severity according to our Security Policy.\n\nThe FIPS modules in 3.6, 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2025-69421)\n\nIssue summary: An invalid or NULL pointer dereference can happen in\nan application processing a malformed PKCS#12 file.\n\nImpact summary: An application processing a malformed PKCS#12 file can be\ncaused to dereference an invalid or NULL pointer on memory read, resulting\nin a Denial of Service.\n\nA type confusion vulnerability exists in PKCS#12 parsing code where\nan ASN1_TYPE union member is accessed without first validating the type,\ncausing an invalid pointer read.\n\nThe location is constrained to a 1-byte address space, meaning any\nattempted pointer manipulation can only target addresses between 0x00 and 0xFF.\nThis range corresponds to the zero page, which is unmapped on most modern\noperating systems and will reliably result in a crash, leading only to a\nDenial of Service. Exploiting this issue also requires a user or application\nto process a maliciously crafted PKCS#12 file. It is uncommon to accept\nuntrusted PKCS#12 files in applications as they are usually used to store\nprivate keys which are trusted by definition. For these reasons, the issue\nwas assessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS12 implementation is outside the OpenSSL FIPS module boundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0 and 1.1.1 are vulnerable to this issue.\n\nOpenSSL 1.0.2 is not affected by this issue.(CVE-2026-22795)\n\nIssue summary: A type confusion vulnerability exists in the signature\nverification of signed PKCS#7 data where an ASN1_TYPE union member is\naccessed without first validating the type, causing an invalid or NULL\npointer dereference when processing malformed PKCS#7 data.\n\nImpact summary: An application performing signature verification of PKCS#7\ndata or calling directly the PKCS7_digest_from_attributes() function can be\ncaused to dereference an invalid or NULL pointer when reading, resulting in\na Denial of Service.\n\nThe function PKCS7_digest_from_attributes() accesses the message digest attribute\nvalue without validating its type. When the type is not V_ASN1_OCTET_STRING,\nthis results in accessing invalid memory through the ASN1_TYPE union, causing\na crash.\n\nExploiting this vulnerability requires an attacker to provide a malformed\nsigned PKCS#7 to an application that verifies it. The impact of the\nexploit is just a Denial of Service, the PKCS7 API is legacy and applications\nshould be using the CMS API instead. For these reasons the issue was\nassessed as Low severity.\n\nThe FIPS modules in 3.5, 3.4, 3.3 and 3.0 are not affected by this issue,\nas the PKCS#7 parsing implementation is outside the OpenSSL FIPS module\nboundary.\n\nOpenSSL 3.6, 3.5, 3.4, 3.3, 3.0, 1.1.1 and 1.0.2 are vulnerable to this issue.(CVE-2026-22796)",
"id": "OESA-2026-1414",
"modified": "2026-08-06T11:10:26Z",
"published": "2026-02-13T11:10:26Z",
"references": [
{
"type": "ADVISORY",
"url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-1414"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-68160"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69418"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69419"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69420"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2025-69421"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22795"
},
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-22796"
}
],
"schema_version": "1.7.2",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "openssl security update",
"upstream": [
"CVE-2025-68160",
"CVE-2025-69418",
"CVE-2025-69419",
"CVE-2025-69420",
"CVE-2025-69421",
"CVE-2026-22795",
"CVE-2026-22796"
]
}
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.