CVE-2026-80322 (GCVE-0-2026-80322)
Vulnerability from cvelistv5 – Published: 2026-11-17 17:44 – Updated: 2026-11-17 17:57
VLAI
EPSS
VEX
Title
Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse
Summary
Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying keep-alive connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-17 17:56 UTC
CWE
Assigner
References
6 references
| URL | Tags |
|---|---|
| https://support.pingidentity.com/s/article/SECADV… | vendor-advisory |
| https://docs.pingidentity.com/pingauthorize/11.1/… | release-notes |
| https://www.pingidentity.com/en/resources/downloa… | product |
| https://docs.pingidentity.com/pingauthorize/11.0/… | release-notes |
| https://docs.pingidentity.com/pingauthorize/10.3/… | release-notes |
| https://docs.pingidentity.com/pingauthorize/10.2/… | release-notes |
Impacted products
1 product
| Vendor | Product | Version | |
|---|---|---|---|
| Ping Identity | PingAuthorize |
Affected:
0 , < 10.2.0.9
(custom)
Affected: 10.3 , < 10.3.0.6 (custom) Affected: 11.0 , < 11.0.0.4 (custom) Affected: 11.1 , < 11.1.0.1 (custom) |
Date Public
2026-11-17 17:00
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-80322",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T17:56:38.787988Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T17:57:19.769Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "PingAuthorize",
"vendor": "Ping Identity",
"versions": [
{
"lessThan": "10.2.0.9",
"status": "affected",
"version": "0",
"versionType": "custom"
},
{
"lessThan": "10.3.0.6",
"status": "affected",
"version": "10.3",
"versionType": "custom"
},
{
"lessThan": "11.0.0.4",
"status": "affected",
"version": "11.0",
"versionType": "custom"
},
{
"lessThan": "11.1.0.1",
"status": "affected",
"version": "11.1",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-17T17:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cspan\u003eUnder specific conditions, \u003cb\u003ePingAuthorize\u003c/b\u003e in \u003cb\u003eGateway mode\u003c/b\u003e can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekeep-alive\u003c/code\u003e\u003cspan\u003e\u0026nbsp;connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.\u003c/span\u003e"
}
],
"value": "Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying\u00a0keep-alive\u00a0connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests."
}
],
"impacts": [
{
"capecId": "CAPEC-26",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-26 Leveraging Race Conditions"
}
]
},
{
"capecId": "CAPEC-131",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-131 Resource Leak Exposure"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/RE:M",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "MODERATE"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-366",
"description": "CWE-366 Race condition within a thread",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-201",
"description": "CWE-201 Insertion of sensitive information into sent data",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-488",
"description": "CWE-488 Exposure of data element to wrong session",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-226",
"description": "CWE-226 Sensitive information in resource not removed before reuse",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-772",
"description": "CWE-772 Missing release of resource after effective lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T17:44:48.866Z",
"orgId": "5998a2e9-ae88-42cd-b6e0-7564fd979f9e",
"shortName": "Ping Identity"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"product"
],
"url": "https://www.pingidentity.com/en/resources/downloads/pingauthorize.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags.\u003c/p\u003e"
}
],
"value": "Upgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags."
}
],
"source": {
"advisory": "SECADV057",
"discovery": "EXTERNAL"
},
"title": "Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAs a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution.\u003c/p\u003e"
}
],
"value": "As a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution."
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "5998a2e9-ae88-42cd-b6e0-7564fd979f9e",
"assignerShortName": "Ping Identity",
"cveId": "CVE-2026-80322",
"datePublished": "2026-11-17T17:44:48.866Z",
"dateReserved": "2026-08-26T08:38:07.043Z",
"dateUpdated": "2026-11-17T17:57:19.769Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-80322",
"date": "2026-11-22",
"epss": "0.00327",
"percentile": "0.26324"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "PingAuthorize",
"vendor": "Ping Identity",
"versions": [
{
"lessThan": "10.2.0.9",
"status": "affected",
"version": "0",
"versionType": "custom"
},
{
"lessThan": "10.3.0.6",
"status": "affected",
"version": "10.3",
"versionType": "custom"
},
{
"lessThan": "11.0.0.4",
"status": "affected",
"version": "11.0",
"versionType": "custom"
},
{
"lessThan": "11.1.0.1",
"status": "affected",
"version": "11.1",
"versionType": "custom"
}
]
}
],
"source": "responsible-disclosure@pingidentity.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying\u00a0keep-alive\u00a0connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests."
}
],
"id": "CVE-2026-80322",
"lastModified": "2026-11-17T18:17:58.950",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:M/U:X",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "MODERATE"
},
"source": "responsible-disclosure@pingidentity.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-80322",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T17:56:38.787988Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-11-17T18:17:58.950",
"references": [
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html"
},
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html"
},
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html"
},
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html"
},
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage"
},
{
"source": "responsible-disclosure@pingidentity.com",
"url": "https://www.pingidentity.com/en/resources/downloads/pingauthorize.html"
}
],
"sourceIdentifier": "responsible-disclosure@pingidentity.com",
"vulnStatus": "Received",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-201"
},
{
"lang": "en",
"value": "CWE-226"
},
{
"lang": "en",
"value": "CWE-366"
},
{
"lang": "en",
"value": "CWE-488"
},
{
"lang": "en",
"value": "CWE-772"
}
],
"source": "responsible-disclosure@pingidentity.com",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-80322",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-11-17T17:56:38.787988Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T17:56:47.066Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"defaultStatus": "unaffected",
"product": "PingAuthorize",
"vendor": "Ping Identity",
"versions": [
{
"lessThan": "10.2.0.9",
"status": "affected",
"version": "0",
"versionType": "custom"
},
{
"lessThan": "10.3.0.6",
"status": "affected",
"version": "10.3",
"versionType": "custom"
},
{
"lessThan": "11.0.0.4",
"status": "affected",
"version": "11.0",
"versionType": "custom"
},
{
"lessThan": "11.1.0.1",
"status": "affected",
"version": "11.1",
"versionType": "custom"
}
]
}
],
"datePublic": "2026-11-17T17:00:00.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cspan\u003eUnder specific conditions, \u003cb\u003ePingAuthorize\u003c/b\u003e in \u003cb\u003eGateway mode\u003c/b\u003e can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying\u0026nbsp;\u003c/span\u003e\u003ccode\u003ekeep-alive\u003c/code\u003e\u003cspan\u003e\u0026nbsp;connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests.\u003c/span\u003e"
}
],
"value": "Under specific conditions, PingAuthorize in Gateway mode can continue an asynchronous upstream request after its 30-second gateway timeout. If the underlying\u00a0keep-alive\u00a0connection is reused for another request before the original response arrives, the late response can be written to the newer exchange. This could cause a subsequent caller to receive response data intended for an earlier request. This behaviour affects all releases and primarily risks unauthorized information disclosure between separate requests."
}
],
"impacts": [
{
"capecId": "CAPEC-26",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-26 Leveraging Race Conditions"
}
]
},
{
"capecId": "CAPEC-131",
"descriptions": [
{
"lang": "en",
"value": "CAPEC-131 Resource Leak Exposure"
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 8.3,
"baseSeverity": "HIGH",
"exploitMaturity": "NOT_DEFINED",
"privilegesRequired": "NONE",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"valueDensity": "NOT_DEFINED",
"vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N/RE:M",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "LOW",
"vulnerabilityResponseEffort": "MODERATE"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-366",
"description": "CWE-366 Race condition within a thread",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-201",
"description": "CWE-201 Insertion of sensitive information into sent data",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-488",
"description": "CWE-488 Exposure of data element to wrong session",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-226",
"description": "CWE-226 Sensitive information in resource not removed before reuse",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-772",
"description": "CWE-772 Missing release of resource after effective lifetime",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-11-17T17:44:48.866Z",
"orgId": "5998a2e9-ae88-42cd-b6e0-7564fd979f9e",
"shortName": "Ping Identity"
},
"references": [
{
"tags": [
"vendor-advisory"
],
"url": "https://support.pingidentity.com/s/article/SECADV057-PingAuthorize-Cross-Request-Response-Leakage"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/11.1/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"product"
],
"url": "https://www.pingidentity.com/en/resources/downloads/pingauthorize.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/11.0/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/10.3/release_notes/paz_release_notes_legacy_home.html"
},
{
"tags": [
"release-notes"
],
"url": "https://docs.pingidentity.com/pingauthorize/10.2/release_notes/paz_release_notes_legacy_home.html"
}
],
"solutions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eUpgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags.\u003c/p\u003e"
}
],
"value": "Upgrade to PingAuthorize 10.2.0.9, 10.3.0.6, 11.0.0.4, or 11.1.0.1, or a later maintenance release on the same version train. For Docker-based DevOps deployments, refreshed images are available under the edge, latest, and 2609 tags."
}
],
"source": {
"advisory": "SECADV057",
"discovery": "EXTERNAL"
},
"title": "Cross-request response leakage in PingAuthorize after asynchronous timeout and connection reuse",
"workarounds": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eAs a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution.\u003c/p\u003e"
}
],
"value": "As a temporary mitigation, disable HTTP keep-alive and connection reuse on any proxies or load balancers positioned in front of the affected PingAuthorize instance. HTTP keep-alive is enabled by default in HTTP/1.1 and later and must be explicitly disabled in the proxy configuration. This workaround does not remove the vulnerability; applying the patch remains the only permanent solution."
}
],
"x_generator": {
"engine": "Vulnogram 1.0.5"
}
}
},
"cveMetadata": {
"assignerOrgId": "5998a2e9-ae88-42cd-b6e0-7564fd979f9e",
"assignerShortName": "Ping Identity",
"cveId": "CVE-2026-80322",
"datePublished": "2026-11-17T17:44:48.866Z",
"dateReserved": "2026-08-26T08:38:07.043Z",
"dateUpdated": "2026-11-17T17:57:19.769Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…