CVE-2026-104816

waiting for further signalsZero needs more public information before it can validate it.

GHSA-p73x-6qrq-34jc ↗EUVD-2026-99238 ↗

no check availablenot proven exploitable
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.
misskey-dev misskey >= 12.0.0
fixed in 2026.7.0
CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
ETK-2026-1495Zero's internal tracking ID, independent of the CVE number., permanent identifier
7d 09h 51msince last run
24mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+1h17m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Misskey RSS widgets in versions 12.0.0 through versions before 2026.7.0 do not adequately restrict link URL schemes. An attacker who can control a configured feed may cause script execution in a user's browser when that user opens a malicious feed-item link.

mitigation

Upgrade Misskey to version 2026.7.0 or later. Until upgrading, remove or avoid RSS feeds that are not fully trusted.

fixed in 2026.7.0

check
no
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.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.63%49th percentile
agent run time
24m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 18:38Z
Δ 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: an exploit technique exists, 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-13 18:38Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1495",
  "cve_id": "CVE-2026-104816",
  "display_id": "CVE-2026-104816",
  "ghsa_id": "GHSA-p73x-6qrq-34jc",
  "euvd_id": "EUVD-2026-99238",
  "status": "published",
  "anchor_state": "anchored",
  "title": "RSS link cross-site scripting in Misskey",
  "summary": "Misskey RSS widgets in versions 12.0.0 through versions before 2026.7.0 do not adequately restrict link URL schemes. An attacker who can control a configured feed may cause script execution in a user's browser when that user opens a malicious feed-item link.",
  "mitigation": "Upgrade Misskey to version 2026.7.0 or later. Until upgrading, remove or avoid RSS feeds that are not fully trusted.",
  "vendor": "misskey-dev",
  "product": "misskey",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.0.0"
      ],
      "ecosystem": "n/a",
      "fixed_versions": [
        "2026.7.0"
      ],
      "package_name": "Misskey",
      "purl": null
    }
  ],
  "cwes": [
    79
  ],
  "cvss_score": 8.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N",
  "epss_score": 0.0063,
  "epss_percentile": 0.4928,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 23.708858383333332,
  "t0_at": "2026-10-13T18:38:06.905000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-13T18:38:06.905000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T18:38:06.905000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104816"
    }
  }
}

published 2026-10-13 19:31Z
last change 2026-10-21 05:31Z

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.