CVE-2026-106510

validatedZero produced an exploit or a check.

GHSA-4488-j8vj-vqqv ↗EUVD-2026-94369 ↗

check availableZero validated a working check for it.not proven exploitableZero has a detection check, but hasn't produced a full working exploit yet.
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
backstage < 1.14.6; >= 1.15.0, < 1.15.4
fixed in 1.14.6, 1.15.4
CWE-183 Permissive List of Allowed Inputs
ETK-2026-947, permanent identifier
pkg:npm/@backstage/plugin-techdocs-node
+16h40mTTV
21mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0hcheck available+16h40magent stopped
0
+6h
+12h
+18h

description

Backstage deployments using affected TechDocs components can execute attacker-supplied operating-system commands on the documentation build host. Exploitation requires an authenticated user who is permitted to register a catalog entity that influences the TechDocs MkDocs configuration.

mitigation

Upgrade backstage to 1.50.5 or 1.54.6 and plugin-techdocs-node to 1.14.6 or 1.15.4, as applicable. Until upgrades are complete, use the external TechDocs builder, limit entity-registration permissions, and review existing MkDocs configuration for suspicious extension settings.

fixed in 1.14.6, 1.15.4

check
available
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.45%37th percentile
agent run time
21m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-07 14:36Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual check: a technique exists and was validated, but no deterministic check could cover this one.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-10-07 14:36Z
    cve_org: trigger signal, started the run

this entry in the feed

GET /api/v1/feed/CVE-2026-106510

{
  "etk_id": "ETK-2026-947",
  "cve_id": "CVE-2026-106510",
  "display_id": "CVE-2026-106510",
  "ghsa_id": "GHSA-4488-j8vj-vqqv",
  "euvd_id": "EUVD-2026-94369",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Command injection in Backstage TechDocs builds",
  "summary": "Backstage deployments using affected TechDocs components can execute attacker-supplied operating-system commands on the documentation build host. Exploitation requires an authenticated user who is permitted to register a catalog entity that influences the TechDocs MkDocs configuration.",
  "mitigation": "Upgrade backstage to 1.50.5 or 1.54.6 and plugin-techdocs-node to 1.14.6 or 1.15.4, as applicable. Until upgrades are complete, use the external TechDocs builder, limit entity-registration permissions, and review existing MkDocs configuration for suspicious extension settings.",
  "vendor": "backstage",
  "product": "backstage",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "< 1.14.6"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.14.6"
      ],
      "package_name": "@backstage/plugin-techdocs-node",
      "purl": "pkg:npm/@backstage/plugin-techdocs-node"
    },
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 1.15.0, < 1.15.4"
      ],
      "ecosystem": "npm",
      "fixed_versions": [
        "1.15.4"
      ],
      "package_name": "@backstage/plugin-techdocs-node",
      "purl": "pkg:npm/@backstage/plugin-techdocs-node"
    }
  ],
  "cwes": [
    183
  ],
  "cvss_score": 7.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:L",
  "epss_score": 0.0045,
  "epss_percentile": 0.3787,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": true,
  "check_confidence_basis": "assessed",
  "exploit": false,
  "pipeline_minutes": 21.459416583333333,
  "t0_at": "2026-10-07T14:36:53.929000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-08T07:16:48.940393+00:00",
      "days": 0.6943867059375,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T14:36:53.929000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-07T14:36:53.929000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-07T14:36:53.929000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-106510"
    }
  }
}

published 2026-10-08 06:55Z
last change 2026-10-21 19:22Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.