CVE-2026-50252 (GCVE-0-2026-50252)

Vulnerability from cvelistv5 – Published: 2026-07-22 13:08 – Updated: 2026-07-22 14:18
VLAI
Title
Possible cache poisoning attack by mapping source port population per thread
Summary
In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled ('so-reuseport: yes') in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks. Upon startup, Unbound randomly partitions the available UDP source port space into disjoint subsets of (almost) equal size, assigning each subset to a specific worker thread. When an incoming DNS query is received, the kernel’s SO_REUSEPORT load balancing mechanism deterministically assigns the query to a socket associated with a particular thread. All outgoing DNS queries generated during the resolution of that request use source ports selected exclusively from the port subset assigned to the corresponding thread. Since these port subsets are disjoint across threads, the source port observed in a resolver’s outgoing query to an authoritative name server serves as a reliable indicator of the worker thread that processed the original client query. A malicious actor can acquire the mapping between incoming UDP source ports (for a given fixed source IP address) and Unbound worker threads and leverage it to conduct DNS cache poisoning attacks by effectively lowering the random port population per thread.
Severity
5.7 (Medium)
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P/U:Amber
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-07-22 14:18 UTC
CWE
  • CWE-349 - Acceptance of Extraneous Untrusted Data With Trusted Data
Assigner
NLnet Labs CNA
CNA scorecard B 82/100 over 76 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
NLnet Labs Unbound Affected: 1.4.22 , < 1.25.2 (semver)
guessed Create a notification for this product.
Date Public
2026-07-22 00:00
Credits
Inbal Schussheim (Hebrew University) Amit Klein (Hebrew University)
Show details on NVD website
To clipboard 

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-50252",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-22T14:18:29.647593Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-07-22T14:18:36.928Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Unbound",
          "vendor": "NLnet Labs",
          "versions": [
            {
              "lessThan": "1.25.2",
              "status": "affected",
              "version": "1.4.22",
              "versionType": "semver"
            }
          ]
        }
      ],
      "credits": [
        {
          "lang": "en",
          "type": "finder",
          "value": "Inbal Schussheim (Hebrew University)"
        },
        {
          "lang": "en",
          "type": "finder",
          "value": "Amit Klein (Hebrew University)"
        }
      ],
      "datePublic": "2026-07-22T00:00:00.000Z",
      "descriptions": [
        {
          "lang": "en",
          "value": "In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled (\u0027so-reuseport: yes\u0027) in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks. Upon startup, Unbound randomly partitions the available UDP source port space into disjoint subsets of (almost) equal size, assigning each subset to a specific worker thread. When an incoming DNS query is received, the kernel\u2019s SO_REUSEPORT load balancing mechanism deterministically assigns the query to a socket associated with a particular thread. All outgoing DNS queries generated during the resolution of that request use source ports selected exclusively from the port subset assigned to the corresponding thread. Since these port subsets are disjoint across threads, the source port observed in a resolver\u2019s outgoing query to an authoritative name server serves as a reliable indicator of the worker thread that processed the original client query. A malicious actor can acquire the mapping between incoming UDP source ports (for a given fixed source IP address) and Unbound worker threads and leverage it to conduct DNS cache poisoning attacks by effectively lowering the random port population per thread."
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "baseScore": 5.7,
            "baseSeverity": "MEDIUM",
            "vectorString": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P/U:Amber",
            "version": "4.0"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-349",
              "description": "CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-07-22T13:08:54.981Z",
        "orgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
        "shortName": "NLnet Labs"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50252.txt"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "value": "This issue is fixed starting with version 1.25.2"
        }
      ],
      "timeline": [
        {
          "lang": "en",
          "time": "2026-04-23T00:00:00.000Z",
          "value": "Issue reported by Inbal Schussheim"
        },
        {
          "lang": "en",
          "time": "2026-04-24T00:00:00.000Z",
          "value": "NLnet Labs shares patch"
        },
        {
          "lang": "en",
          "time": "2026-04-29T00:00:00.000Z",
          "value": "Inbal Schussheim verifies patch"
        },
        {
          "lang": "en",
          "time": "2026-07-22T00:00:00.000Z",
          "value": "Fixes released with version 1.25.2"
        }
      ],
      "title": "Possible cache poisoning attack by mapping source port population per thread",
      "x_generator": {
        "engine": "cvelib 1.8.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
    "assignerShortName": "NLnet Labs",
    "cveId": "CVE-2026-50252",
    "datePublished": "2026-07-22T13:08:54.981Z",
    "dateReserved": "2026-06-22T12:35:21.348Z",
    "dateUpdated": "2026-07-22T14:18:36.928Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2026-50252",
      "date": "2026-11-10",
      "epss": "0.00172",
      "percentile": "0.06621"
    },
    "microsoft_vex": {
      "current_release_date": "2026-07-23T14:44:57.000Z",
      "cve": "CVE-2026-50252",
      "id": "msrc_CVE-2026-50252",
      "initial_release_date": "2026-07-23T01:05:16.000Z",
      "product_status:fixed": "1",
      "product_status:known_affected": "1",
      "source": "Microsoft CSAF VEX",
      "status": "final",
      "title": "Possible cache poisoning attack by mapping source port population per thread",
      "url": "https://msrc.microsoft.com/csaf/vex/2026/msrc_cve-2026-50252.json",
      "version": "2"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Unbound",
                "vendor": "NLnet Labs",
                "versions": [
                  {
                    "lessThan": "1.25.2",
                    "status": "affected",
                    "version": "1.4.22",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "sep@nlnetlabs.nl"
          }
        ],
        "configurations": [
          {
            "nodes": [
              {
                "cpeMatch": [
                  {
                    "criteria": "cpe:2.3:a:nlnetlabs:unbound:*:*:*:*:*:*:*:*",
                    "matchCriteriaId": "F361362B-563C-491C-806A-B7078E1F2357",
                    "versionEndExcluding": "1.25.2",
                    "versionStartIncluding": "1.4.22",
                    "vulnerable": true
                  }
                ],
                "negate": false,
                "operator": "OR"
              }
            ]
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled (\u0027so-reuseport: yes\u0027) in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks. Upon startup, Unbound randomly partitions the available UDP source port space into disjoint subsets of (almost) equal size, assigning each subset to a specific worker thread. When an incoming DNS query is received, the kernel\u2019s SO_REUSEPORT load balancing mechanism deterministically assigns the query to a socket associated with a particular thread. All outgoing DNS queries generated during the resolution of that request use source ports selected exclusively from the port subset assigned to the corresponding thread. Since these port subsets are disjoint across threads, the source port observed in a resolver\u2019s outgoing query to an authoritative name server serves as a reliable indicator of the worker thread that processed the original client query. A malicious actor can acquire the mapping between incoming UDP source ports (for a given fixed source IP address) and Unbound worker threads and leverage it to conduct DNS cache poisoning attacks by effectively lowering the random port population per thread."
          },
          {
            "lang": "es",
            "value": "En NLnet Labs Unbound 1.4.22 hasta e incluyendo 1.25.1, el puerto de origen UDP est\u00e1 aleatorizado y est\u00e1 destinado a servir como un valor secreto que aumenta la entrop\u00eda de las transacciones DNS. Cuando las pol\u00edticas de balanceo de carga del resolvedor dependen del puerto de origen mientras su resultado es revelado, este secreto se ve socavado. La vulnerabilidad surge cuando la pol\u00edtica de balanceo de carga es consistente con respecto al puerto de origen UDP entrante y la direcci\u00f3n IP, mientras depende en gran medida del puerto de origen UDP entrante como fuente de aleatorizaci\u00f3n. Cuando la opci\u00f3n de configuraci\u00f3n SO_REUSEPORT est\u00e1 habilitada (\u2019so-reuseport: yes\u2019) en Unbound (por defecto), cumple estas condiciones, haci\u00e9ndolo vulnerable a ataques de envenenamiento de cach\u00e9 DNS. Al iniciar, Unbound particiona aleatoriamente el espacio de puertos de origen UDP disponible en subconjuntos disjuntos de tama\u00f1o (casi) igual, asignando cada subconjunto a un hilo de trabajador espec\u00edfico. Cuando se recibe una consulta DNS entrante, el mecanismo de balanceo de carga SO_REUSEPORT del kernel asigna la consulta de forma determinista a un socket asociado con un hilo particular. Todas las consultas DNS salientes generadas durante la resoluci\u00f3n de esa solicitud usan puertos de origen seleccionados exclusivamente del subconjunto de puertos asignado al hilo correspondiente. Dado que estos subconjuntos de puertos son disjuntos entre hilos, el puerto de origen observado en la consulta saliente de un resolvedor a un servidor de nombres autoritativo sirve como un indicador fiable del hilo de trabajador que proces\u00f3 la consulta original del cliente. Un actor malicioso puede adquirir el mapeo entre puertos de origen UDP entrantes (para una direcci\u00f3n IP de origen fija dada) y los hilos de trabajador de Unbound y aprovecharlo para llevar a cabo ataques de envenenamiento de cach\u00e9 DNS al reducir efectivamente la poblaci\u00f3n de puertos aleatorios por hilo."
          }
        ],
        "id": "CVE-2026-50252",
        "lastModified": "2026-10-24T13:10:00.147",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "ADJACENT_NETWORK",
                "availabilityImpact": "HIGH",
                "baseScore": 9.3,
                "baseSeverity": "CRITICAL",
                "confidentialityImpact": "NONE",
                "integrityImpact": "HIGH",
                "privilegesRequired": "NONE",
                "scope": "CHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 2.8,
              "impactScore": 5.8,
              "source": "nvd@nist.gov",
              "type": "Primary"
            }
          ],
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "ADJACENT",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 5.7,
                "baseSeverity": "MEDIUM",
                "confidentialityRequirement": "NOT_DEFINED",
                "exploitMaturity": "PROOF_OF_CONCEPT",
                "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": "AMBER",
                "subAvailabilityImpact": "HIGH",
                "subConfidentialityImpact": "NONE",
                "subIntegrityImpact": "HIGH",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:Amber",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "NONE",
                "vulnIntegrityImpact": "HIGH",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "sep@nlnetlabs.nl",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-50252",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-07-22T14:18:29.647593Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-07-22T14:17:20.627",
        "references": [
          {
            "source": "sep@nlnetlabs.nl",
            "tags": [
              "Vendor Advisory"
            ],
            "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50252.txt"
          }
        ],
        "sourceIdentifier": "sep@nlnetlabs.nl",
        "vulnStatus": "Analyzed",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-349"
              }
            ],
            "source": "sep@nlnetlabs.nl",
            "type": "Secondary"
          }
        ]
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Moderate",
      "current_release_date": "2026-11-07T04:56:36+00:00",
      "cve": "CVE-2026-50252",
      "id": "CVE-2026-50252",
      "initial_release_date": "2026-07-22T13:08:54.981000+00:00",
      "product_status:fixed": "200",
      "product_status:known_affected": "7",
      "product_status:known_not_affected": "5",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "unbound: Unbound: DNS cache poisoning via UDP source port predictability",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-50252.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-09-18T00:53:27Z",
      "cve": "CVE-2026-50252",
      "id": "CVE-2026-50252",
      "initial_release_date": "2026-07-26T23:31:50Z",
      "product_status:known_affected": "56",
      "product_status:recommended": "98",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2026-50252",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/cve-2026-50252.json",
      "version": "12"
    },
    "vulnrichment": {
      "containers": {
        "adp": [
          {
            "metrics": [
              {
                "other": {
                  "content": {
                    "id": "CVE-2026-50252",
                    "options": [
                      {
                        "Exploitation": "none"
                      },
                      {
                        "Automatable": "no"
                      },
                      {
                        "Technical Impact": "partial"
                      }
                    ],
                    "role": "CISA Coordinator",
                    "timestamp": "2026-07-22T14:18:29.647593Z",
                    "version": "2.0.3"
                  },
                  "type": "ssvc"
                }
              }
            ],
            "providerMetadata": {
              "dateUpdated": "2026-07-22T14:18:33.750Z",
              "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "shortName": "CISA-ADP"
            },
            "title": "CISA ADP Vulnrichment"
          }
        ],
        "cna": {
          "affected": [
            {
              "defaultStatus": "unaffected",
              "product": "Unbound",
              "vendor": "NLnet Labs",
              "versions": [
                {
                  "lessThan": "1.25.2",
                  "status": "affected",
                  "version": "1.4.22",
                  "versionType": "semver"
                }
              ]
            }
          ],
          "credits": [
            {
              "lang": "en",
              "type": "finder",
              "value": "Inbal Schussheim (Hebrew University)"
            },
            {
              "lang": "en",
              "type": "finder",
              "value": "Amit Klein (Hebrew University)"
            }
          ],
          "datePublic": "2026-07-22T00:00:00.000Z",
          "descriptions": [
            {
              "lang": "en",
              "value": "In NLnet Labs Unbound 1.4.22 up to and including 1.25.1, UDP source port is randomized and intended to serve as a secret value that increases the entropy of DNS transactions. When resolver load balancing policies depend on the source port while their outcome is revealed this secrecy is undermined. The vulnerability arises when the load balancing policy is consistent with respect to the incoming source UDP port and IP address while heavily depending on the incoming source UDP port as a randomization source. When the SO_REUSEPORT configuration option is enabled (\u0027so-reuseport: yes\u0027) in Unbound (by default), it meets these conditions, making it vulnerable for DNS cache poisoning attacks. Upon startup, Unbound randomly partitions the available UDP source port space into disjoint subsets of (almost) equal size, assigning each subset to a specific worker thread. When an incoming DNS query is received, the kernel\u2019s SO_REUSEPORT load balancing mechanism deterministically assigns the query to a socket associated with a particular thread. All outgoing DNS queries generated during the resolution of that request use source ports selected exclusively from the port subset assigned to the corresponding thread. Since these port subsets are disjoint across threads, the source port observed in a resolver\u2019s outgoing query to an authoritative name server serves as a reliable indicator of the worker thread that processed the original client query. A malicious actor can acquire the mapping between incoming UDP source ports (for a given fixed source IP address) and Unbound worker threads and leverage it to conduct DNS cache poisoning attacks by effectively lowering the random port population per thread."
            }
          ],
          "metrics": [
            {
              "cvssV4_0": {
                "baseScore": 5.7,
                "baseSeverity": "MEDIUM",
                "vectorString": "CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:H/SA:H/E:P/U:Amber",
                "version": "4.0"
              },
              "format": "CVSS",
              "scenarios": [
                {
                  "lang": "en",
                  "value": "GENERAL"
                }
              ]
            }
          ],
          "problemTypes": [
            {
              "descriptions": [
                {
                  "cweId": "CWE-349",
                  "description": "CWE-349: Acceptance of Extraneous Untrusted Data With Trusted Data",
                  "lang": "en",
                  "type": "CWE"
                }
              ]
            }
          ],
          "providerMetadata": {
            "dateUpdated": "2026-07-22T13:08:54.981Z",
            "orgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
            "shortName": "NLnet Labs"
          },
          "references": [
            {
              "tags": [
                "vendor-advisory"
              ],
              "url": "https://www.nlnetlabs.nl/downloads/unbound/CVE-2026-50252.txt"
            }
          ],
          "solutions": [
            {
              "lang": "en",
              "value": "This issue is fixed starting with version 1.25.2"
            }
          ],
          "timeline": [
            {
              "lang": "en",
              "time": "2026-04-23T00:00:00.000Z",
              "value": "Issue reported by Inbal Schussheim"
            },
            {
              "lang": "en",
              "time": "2026-04-24T00:00:00.000Z",
              "value": "NLnet Labs shares patch"
            },
            {
              "lang": "en",
              "time": "2026-04-29T00:00:00.000Z",
              "value": "Inbal Schussheim verifies patch"
            },
            {
              "lang": "en",
              "time": "2026-07-22T00:00:00.000Z",
              "value": "Fixes released with version 1.25.2"
            }
          ],
          "title": "Possible cache poisoning attack by mapping source port population per thread",
          "x_generator": {
            "engine": "cvelib 1.8.0"
          }
        }
      },
      "cveMetadata": {
        "assignerOrgId": "206fc3a0-e175-490b-9eaa-a5738056c9f6",
        "assignerShortName": "NLnet Labs",
        "cveId": "CVE-2026-50252",
        "datePublished": "2026-07-22T13:08:54.981Z",
        "dateReserved": "2026-06-22T12:35:21.348Z",
        "dateUpdated": "2026-07-22T14:18:36.928Z",
        "state": "PUBLISHED"
      },
      "dataType": "CVE_RECORD",
      "dataVersion": "5.2"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




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.

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.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
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…




    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.