CVE-2026-130089 (GCVE-0-2026-130089)

Vulnerability from cvelistv5 – Published: 2026-11-18 20:20 – Updated: 2026-11-18 21:19
VLAI
Title
temporal-proxy request namespace can redirect a templated upstream and leak its API key
Summary
A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream's hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.
SSVC
Exploitation: none Automatable: no Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-11-18 21:19 UTC
CWE
  • CWE-918 - Server-Side Request Forgery
Assigner
Temporal CNA under the mitre root
CNA scorecard A 96/100 over 20 records in the last 180 days details
Impacted products
Vendor Product Version CPE status
Temporal Technologies, Inc. temporal-proxy Affected: 0.1.0 , ≤ 0.10.1 (semver)
Affected: 1.0.0 , < 1.0.2 (semver)
Affected: 1.1.0 , < 1.1.2 (semver)
Affected: 1.2.0 , < 1.2.1 (semver)
guessed Create a notification for this product.
Show details on NVD website

{
  "containers": {
    "adp": [
      {
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2026-130089",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "no"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T21:19:48.680937Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2026-11-18T21:19:56.314Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "collectionURL": "https://pkg.go.dev",
          "defaultStatus": "unaffected",
          "packageName": "github.com/temporalio/temporal-proxy",
          "product": "temporal-proxy",
          "programFiles": [
            "internal/proxy/resolver.go",
            "internal/config/upstream.go"
          ],
          "programRoutines": [
            {
              "name": "DynamicResolver.Resolve"
            },
            {
              "name": "invalidAddress"
            }
          ],
          "repo": "https://github.com/temporalio/temporal-proxy",
          "vendor": "Temporal Technologies, Inc.",
          "versions": [
            {
              "lessThanOrEqual": "0.10.1",
              "status": "affected",
              "version": "0.1.0",
              "versionType": "semver"
            },
            {
              "lessThan": "1.0.2",
              "status": "affected",
              "version": "1.0.0",
              "versionType": "semver"
            },
            {
              "lessThan": "1.1.2",
              "status": "affected",
              "version": "1.1.0",
              "versionType": "semver"
            },
            {
              "lessThan": "1.2.1",
              "status": "affected",
              "version": "1.2.0",
              "versionType": "semver"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eExploitation requires all of the following: an upstream whose hostPort template includes the request namespace or request metadata; a static outbound credential on that upstream; TLS verified against the system trust store with no literal tls.serverName; and a route, such as a default route, that sends the caller\u0027s namespace to that upstream. The published Temporal Cloud configuration example has this shape but listens on loopback only.\u003c/p\u003e"
            }
          ],
          "value": "Exploitation requires all of the following: an upstream whose hostPort template includes the request namespace or request metadata; a static outbound credential on that upstream; TLS verified against the system trust store with no literal tls.serverName; and a route, such as a default route, that sends the caller\u0027s namespace to that upstream. The published Temporal Cloud configuration example has this shape but listens on loopback only."
        },
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eAttack Requirements is Present because the deployment must use the upstream configuration above. Privileges Required is Low because the score assumes inbound authentication is configured; under the default, which admits every caller, no credential is needed. The subsequent-system metrics are High because the key works against the upstream Temporal service independently of the proxy.\u003c/p\u003e"
            }
          ],
          "value": "Attack Requirements is Present because the deployment must use the upstream configuration above. Privileges Required is Low because the score assumes inbound authentication is configured; under the default, which admits every caller, no credential is needed. The subsequent-system metrics are High because the key works against the upstream Temporal service independently of the proxy."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eA caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream\u0027s hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach.\u003c/p\u003e"
            }
          ],
          "value": "A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream\u0027s hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach."
        }
      ],
      "impacts": [
        {
          "descriptions": [
            {
              "lang": "en",
              "value": "Disclosure of the proxy\u0027s static upstream API key to a host the caller chooses. With the key, the caller can read and modify every namespace it authorizes on the upstream Temporal service, without going through the proxy, including starting, signaling, and terminating Workflows and deleting Schedules. The proxy\u0027s own data and availability are not affected."
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV4_0": {
            "Automatable": "NOT_DEFINED",
            "Recovery": "NOT_DEFINED",
            "Safety": "NOT_DEFINED",
            "attackComplexity": "LOW",
            "attackRequirements": "PRESENT",
            "attackVector": "NETWORK",
            "baseScore": 7.3,
            "baseSeverity": "HIGH",
            "exploitMaturity": "NOT_DEFINED",
            "privilegesRequired": "LOW",
            "providerUrgency": "NOT_DEFINED",
            "subAvailabilityImpact": "HIGH",
            "subConfidentialityImpact": "HIGH",
            "subIntegrityImpact": "HIGH",
            "userInteraction": "NONE",
            "valueDensity": "NOT_DEFINED",
            "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H",
            "version": "4.0",
            "vulnAvailabilityImpact": "NONE",
            "vulnConfidentialityImpact": "HIGH",
            "vulnIntegrityImpact": "NONE",
            "vulnerabilityResponseEffort": "NOT_DEFINED"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-918",
              "description": "CWE-918: Server-Side Request Forgery",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-11-18T20:20:49.623Z",
        "orgId": "61241ed8-fa44-4f23-92db-b8c443751968",
        "shortName": "Temporal"
      },
      "references": [
        {
          "name": "Upstream address validation in temporal-proxy 1.2.0, which rejects only empty hosts and labels",
          "tags": [
            "product"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282"
        },
        {
          "name": "Fix pull request",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/pull/284"
        },
        {
          "name": "Fix commit",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8"
        },
        {
          "name": "Backport pull request for the 1.0 release line",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/pull/294"
        },
        {
          "name": "Backport commit on releases/v1.0.x",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061"
        },
        {
          "name": "Backport pull request for the 1.1 release line",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/pull/293"
        },
        {
          "name": "Backport commit on releases/v1.1.x",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90"
        },
        {
          "name": "Backport pull request for the 1.2 release line",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/pull/292"
        },
        {
          "name": "Backport commit on releases/v1.2.x",
          "tags": [
            "patch"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a"
        },
        {
          "name": "temporal-proxy 1.0.2",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
        },
        {
          "name": "temporal-proxy 1.1.2",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
        },
        {
          "name": "temporal-proxy 1.2.1",
          "tags": [
            "release-notes"
          ],
          "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eUpgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. Releases before 1.0.0 receive no fix.\u003c/p\u003e"
            }
          ],
          "value": "Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. Releases before 1.0.0 receive no fix."
        }
      ],
      "source": {
        "discovery": "INTERNAL"
      },
      "title": "temporal-proxy request namespace can redirect a templated upstream and leak its API key",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cp\u003eUse fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces.\u003c/p\u003e"
            }
          ],
          "value": "Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces."
        }
      ]
    }
  },
  "cveMetadata": {
    "assignerOrgId": "61241ed8-fa44-4f23-92db-b8c443751968",
    "assignerShortName": "Temporal",
    "cveId": "CVE-2026-130089",
    "datePublished": "2026-11-18T20:20:49.623Z",
    "dateReserved": "2026-11-16T20:59:57.535Z",
    "dateUpdated": "2026-11-18T21:19:56.314Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "collectionURL": "https://pkg.go.dev",
                "defaultStatus": "unaffected",
                "packageName": "github.com/temporalio/temporal-proxy",
                "product": "temporal-proxy",
                "programFiles": [
                  "internal/proxy/resolver.go",
                  "internal/config/upstream.go"
                ],
                "programRoutines": [
                  {
                    "name": "DynamicResolver.Resolve"
                  },
                  {
                    "name": "invalidAddress"
                  }
                ],
                "repo": "https://github.com/temporalio/temporal-proxy",
                "vendor": "Temporal Technologies, Inc.",
                "versions": [
                  {
                    "lessThanOrEqual": "0.10.1",
                    "status": "affected",
                    "version": "0.1.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "1.0.2",
                    "status": "affected",
                    "version": "1.0.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "1.1.2",
                    "status": "affected",
                    "version": "1.1.0",
                    "versionType": "semver"
                  },
                  {
                    "lessThan": "1.2.1",
                    "status": "affected",
                    "version": "1.2.0",
                    "versionType": "semver"
                  }
                ]
              }
            ],
            "source": "security@temporal.io"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "A caller who can send requests to the temporal-proxy gRPC listener can obtain the static API key of an upstream whose address is templated from the request namespace, and then use that key directly against the upstream Temporal service. temporal-proxy does not validate the request namespace before rendering it into a templated upstream address, so when an upstream\u0027s hostPort is templated from the namespace, as in the published Temporal Cloud configuration example, a crafted namespace changes the host the proxy dials. If that upstream verifies TLS against the system trust store and sets no literal server name, a caller-controlled host with a publicly trusted certificate passes verification and receives the key. The built-in static-token and JWKS authenticators do not restrict namespaces, so any caller they admit can do this; an external authenticator that admits only listed namespaces prevents it. temporal-proxy versions 0.1.0 through 1.2.0 are affected. The issue is fixed in 1.0.2, 1.1.2, and 1.2.1, and releases before 1.0.0 receive no fix. Upgrade to the fixed release for the deployed minor release line, and rotate any upstream API key that untrusted callers could reach."
          }
        ],
        "id": "CVE-2026-130089",
        "lastModified": "2026-11-18T22:17:18.580",
        "metrics": {
          "cvssMetricV40": [
            {
              "cvssData": {
                "Automatable": "NOT_DEFINED",
                "Recovery": "NOT_DEFINED",
                "Safety": "NOT_DEFINED",
                "attackComplexity": "LOW",
                "attackRequirements": "PRESENT",
                "attackVector": "NETWORK",
                "availabilityRequirement": "NOT_DEFINED",
                "baseScore": 7.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": "LOW",
                "providerUrgency": "NOT_DEFINED",
                "subAvailabilityImpact": "HIGH",
                "subConfidentialityImpact": "HIGH",
                "subIntegrityImpact": "HIGH",
                "userInteraction": "NONE",
                "valueDensity": "NOT_DEFINED",
                "vectorString": "CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
                "version": "4.0",
                "vulnAvailabilityImpact": "NONE",
                "vulnConfidentialityImpact": "HIGH",
                "vulnIntegrityImpact": "NONE",
                "vulnerabilityResponseEffort": "NOT_DEFINED"
              },
              "source": "security@temporal.io",
              "type": "Secondary"
            }
          ],
          "ssvcV203": [
            {
              "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
              "ssvcData": {
                "id": "CVE-2026-130089",
                "options": [
                  {
                    "exploitation": "none"
                  },
                  {
                    "automatable": "no"
                  },
                  {
                    "technicalImpact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2026-11-18T21:19:48.680937Z",
                "version": "2.0.3"
              }
            }
          ]
        },
        "published": "2026-11-18T21:17:48.933",
        "references": [
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/blob/v1.2.0/internal/proxy/resolver.go#L259-L282"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/commit/b902dcfcc1d32288c9d1d14fc2c71d2e8052a4b8"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/commit/c73636037045e31162420a13f6f0aee48ce3313a"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/commit/cd60785edd81cfa0c599b17f94ee7de7d8eaf061"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/commit/dfb4b83f0ed20db5a9f772dd249470f7f7f15c90"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/pull/284"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/pull/292"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/pull/293"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/pull/294"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.0.2"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.1.2"
          },
          {
            "source": "security@temporal.io",
            "url": "https://github.com/temporalio/temporal-proxy/releases/tag/v1.2.1"
          }
        ],
        "sourceIdentifier": "security@temporal.io",
        "vulnStatus": "Received",
        "weaknesses": [
          {
            "description": [
              {
                "lang": "en",
                "value": "CWE-918"
              }
            ],
            "source": "security@temporal.io",
            "type": "Secondary"
          }
        ]
      }
    }
  }
}


Solutions

CNA · Temporal
Upgrade to temporal-proxy 1.0.2, 1.1.2, or 1.2.1, as appropriate for the deployed minor release line. Fixed releases reject a request whose templated upstream address does not render to a plain host name or IP address with an optional port, or whose templated TLS server name is not a plain host name. They also refuse at configuration load a templated hostPort or tls.serverName whose host does not end in a literal domain, as in {{ .RemoteNamespace }}.tmprl.cloud:7233, so a configuration that templates the whole host must be changed before upgrading. Rotate any upstream API key held by an affected deployment that untrusted callers could reach. Releases before 1.0.0 receive no fix.

Workarounds

CNA · Temporal
Use fixed upstream addresses, or routing rules that match literal namespace names, with no default or system route to a templated upstream. Alternatively, set a literal tls.serverName on the templated upstream, or use an external authenticator that admits only listed namespaces.

Configurations

CNA · Temporal
Exploitation requires all of the following: an upstream whose hostPort template includes the request namespace or request metadata; a static outbound credential on that upstream; TLS verified against the system trust store with no literal tls.serverName; and a route, such as a default route, that sends the caller's namespace to that upstream. The published Temporal Cloud configuration example has this shape but listens on loopback only.
Attack Requirements is Present because the deployment must use the upstream configuration above. Privileges Required is Low because the score assumes inbound authentication is configured; under the default, which admits every caller, no credential is needed. The subsequent-system metrics are High because the key works against the upstream Temporal service independently of the proxy.

Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

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.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    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.