Security readout for executives and security teams
Plain-English summary
CVE-2026-28355 is a low-severity self-XSS issue in the PWA Canarytoken feature. A token creator could place JavaScript in a PWA token title, causing it to run when the install page is viewed. Canarytokens.org is patched. Self-hosted users may be exposed if running versions before sha-7ff0e12.
Executive priority
Treat as routine maintenance, not an emergency. The issue is low severity, requires user interaction, and the advisory reports no sensitive session disclosure. Prioritize confirming whether self-hosted Canarytokens exists, then update during the next suitable maintenance window.
Technical view
Thinkst Canarytokens before sha-7ff0e12 did not sufficiently neutralize JavaScript in the PWA Canarytoken title field. The script executes on the PWA install page. The advisory describes this as self-XSS: an attacker can send a crafted install link, but the source states no sensitive information, such as session information, is disclosed to the malicious actor.
Likely exposure
Exposure is limited to Canarytokens deployments using the PWA Canarytoken feature on versions before sha-7ff0e12. The hosted Canarytokens.org service is reported patched. Self-hosted Docker deployments should verify their image version or commit level.
Exploitation context
The CVE record marks exploitation as unproven, and CISA KEV is not indicated in the provided data. Exploitation requires user interaction: a victim must open the crafted PWA install link. The documented impact is limited, with no sensitive-information disclosure reported by the advisory.
Researcher notes
This is CWE-79 stored self-XSS in the PWA Canarytoken title field. The affected range is versions before sha-7ff0e12. Avoid assuming broader Canarytokens exposure beyond the PWA token install page. Public sources do not show active exploitation or a higher-impact data theft path.
Mitigation direction
- Canarytokens.org users: no action is indicated; the hosted service is reported patched.
- Self-hosted users: update by pulling the latest Docker image.
- Alternatively, use any Docker image after sha-7ff0e12.
- Review vendor advisory for any deployment-specific instructions.
Validation and detection
- Identify whether your organization runs self-hosted Thinkst Canarytokens.
- Confirm whether PWA Canarytokens are enabled or used.
- Check the running Docker image or source revision against sha-7ff0e12.
- Verify the deployment is updated to a post-sha-7ff0e12 image.
- Review logs or tickets for suspicious PWA install links if relevant.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCredential and access behavior lookup
The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupContainer behavior lookup
The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-28355 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 1.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U——Primary CVE scoreVulnerability scoring details
Base CVSS 4.0 score
1.3LowVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:U
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/thinkst/canarytokens/security/advisories/GHSA-6734-fqcj-x5h3CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.