Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.6amended

@tinacms/web-components: tina-markdown writes rich-text link URLs into href without scheme validation, allowing stored XSS

CVE-2026-108260GHSA-c42q-qvc3-j6vg

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (@tinacms/web-components 0.2.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
EPSS
  • CVE-2026-108260: 0.25% estimated exploitation activity in the next 30 days; percentile 16.96 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary <tina-markdown renders a rich-text AST into the DOM and, for a nodes, assigns the node's URL straight to the anchor's href with no scheme check. A link authored in the CMS as javascript:… renders as a live javascript: anchor, so a visitor who clicks it executes attacker-supplied script in the site's origin. Every sibling renderer in the repository already sanitizes these URLs; this one does not. Details The unvalidated sink: node.url comes from the content attribute the site populates from the TinaCMS content API (:169-176), i.e. whatever a content author typed into a rich-text field. The DOMPurify call at :68 handles only raw-HTML node values and returns before the anchor branch, so it never inspects node.url. Line 75 is a direct property assignment — no HTML parser, no sanitizer. The mode: 'open' shadow root (:164-167) provides no script isolation. The guard that exists in every sibling renderer: tina-markdown.js:75 is the only rich-text link sink in the repository that…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-c42q-qvc3-j6vg

  2. Revision 2 · amended ·

    Amended from osv record GHSA-c42q-qvc3-j6vg

  3. Revision 1 · created ·

    Published from ghsa record GHSA-c42q-qvc3-j6vg

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-108260

Advisory: @tinacms/web-components: `tina-markdown` writes rich-text link URLs into `href` without scheme validation, allowing stored XSS
IDs: CVE-2026-108260, GHSA-c42q-qvc3-j6vg
Record: https://patchnext.com/advisories/cve-2026-108260 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.6)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @tinacms/web-components 0.2.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @tinacms/web-components: affected <= 0.2.0; fixed in 0.2.1

## Suggested inspection (read-only)
- `npm ls @tinacms/web-components --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @tinacms/web-components.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c42q-qvc3-j6vg (GitHub-reviewed advisory GHSA-c42q-qvc3-j6vg lists affected ranges: npm @tinacms/web-components >=0 <=0.2.0)
- Verified: https://osv.dev/vulnerability/GHSA-c42q-qvc3-j6vg (OSV record GHSA-c42q-qvc3-j6vg lists affected ranges: npm @tinacms/web-components >=0 <0.2.1 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…