Skip to main content
VulnerabilityPublished

CVE-2026-65655: Temporal UI Server · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute

Affects Temporal UI ServerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 2.3 Low : upgrade to 2.53.2 when convenient.

Data as of 10 Nov 2026, 23:24 UTC

CVSS 4.0 base score
2.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.53.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 11 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 11 Nov 2026.

What to do

Upgrade Temporal UI Server and github.com/temporalio/ui-server/v2 to 2.53.2.

Affected software

ProductAffectedFixed in
Temporal Technologies, Inc.Temporal UI ServerAffected
  • >=2.7.0 <2.53.2
Fixed in
  • 2.53.2
Gogithub.com/temporalio/ui-server/v2pkg:golang/github.com/temporalio/ui-server/v2Other threatsAffected
  • >=2.7.0 <2.53.2
Fixed in
  • 2.53.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Mitigation includes ensuring TLS is re-encrypted between the reverse proxy and Temporal UI Server or configuring effective HSTS and HTTPS-only warnings to prevent downgrade to HTTP. Avoid terminating TLS at a proxy that forwards to the server over HTTP without secure cookie handling. These measures prevent the demonstrated disclosure path.

Description

When OAuth authentication is enabled and browser-facing TLS terminates at a reverse proxy that forwards the callback to Temporal UI Server over HTTP, affected versions derive authentication-cookie Secure attributes from the proxy-to-server connection. Temporal UI Server can therefore issue access-token cookies, and refresh-token cookies when provided by the identity provider, without Secure even though the browser completed login over HTTPS. A victim who visits attacker-controlled content while a credential remains live may expose that credential only if the attacker can also steer traffic for the UI hostname, prevent the browser's HTTPS connection from succeeding, serve the hostname over HTTP, and read a later same-site plaintext request. A malicious website alone cannot read the cookie, and passive observation of a successful TLS connection is insufficient. Effective HSTS, a blocking HTTPS-only warning, or TLS re-encryption between the proxy and Temporal UI Server prevents the demonstrated disclosure path. A recovered credential may be replayed within the victim's assigned permissions. Refresh-token replay additionally depends on the identity provider's issuance, expiry, rotation, and reuse-detection behavior.

References

Community reviews

Loading reviews…