← back to feed
CVE-2026-104817

CVE-2026-104817

validatedZero produced an exploit or a check.

GHSA-4x7v-qx8f-g3p8 ↗EUVD-2026-99239 ↗

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.
misskey-dev misskey >= 12.112.1
fixed in 2026.7.0
CWE-405 Asymmetric Resource Consumption (Amplification)
ETK-2026-1494Zero's internal tracking ID, independent of the CVE number., permanent identifier
cvss8.7cna vendorCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:L/SI:N/SA:L
+1h13mTTV
23mAI analysisAnalysis: how long the AI spent reversing this signal.
Check if you are vulnerable
timeline
0 = trigger signal
trigger signal (cve.org) +0mcheck available+73magent stopped
0
+15min
+30min
+45min
+60min

description

Misskey versions 12.112.1 through versions before 2026.7.0 expose an RSS-fetch API that does not sufficiently constrain request volume or response size. An unauthenticated attacker can cause outbound requests and parsing work that exhaust instance resources, amplify traffic to other systems, or reach services accessible from the instance; federation need not be enabled.

mitigation

Upgrade the misskey package to version 2026.7.0 or later. Until the upgrade is complete, restrict unauthenticated access to the RSS-fetch API to reduce exposure.

fixed in 2026.7.0

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.
deterministic
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.46%38th percentile
agent run time
23m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-13 18:39Z
Δ 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

Check only, differential: the check fires on the vulnerable build and is silent on the patched one.

source signals

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

  1. 2026-10-13 18:39Z
    cve_org: trigger signal, started the run
    https://www.cve.org/CVERecord?id=CVE-2026-104817

this entry in the feed

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

{
  "etk_id": "ETK-2026-1494",
  "cve_id": "CVE-2026-104817",
  "display_id": "CVE-2026-104817",
  "ghsa_id": "GHSA-4x7v-qx8f-g3p8",
  "euvd_id": "EUVD-2026-99239",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated RSS fetch resource exhaustion in Misskey",
  "summary": "Misskey versions 12.112.1 through versions before 2026.7.0 expose an RSS-fetch API that does not sufficiently constrain request volume or response size. An unauthenticated attacker can cause outbound requests and parsing work that exhaust instance resources, amplify traffic to other systems, or reach services accessible from the instance; federation need not be enabled.",
  "mitigation": "Upgrade the misskey package to version 2026.7.0 or later. Until the upgrade is complete, restrict unauthenticated access to the RSS-fetch API to reduce exposure.",
  "vendor": "misskey-dev",
  "product": "misskey",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 12.112.1"
      ],
      "ecosystem": "n/a",
      "fixed_versions": [
        "2026.7.0"
      ],
      "package_name": "Misskey",
      "purl": null
    }
  ],
  "cwes": [
    405
  ],
  "cvss_score": 8.7,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:L/SI:N/SA:L",
  "epss_score": 0.0046,
  "epss_percentile": 0.3852,
  "epss_asof": "2026-10-20",
  "automation": "deterministic",
  "check": true,
  "check_confidence_basis": "differential",
  "exploit": false,
  "pipeline_minutes": 22.850485733333333,
  "t0_at": "2026-10-13T18:39:30.169000+00:00",
  "signals": {
    "check": {
      "at": "2026-10-13T19:52:28.176167+00:00",
      "days": 0.05067137924768519,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T18:39:30.169000+00:00",
      "url": null
    },
    "trigger_signal": {
      "at": "2026-10-13T18:39:30.169000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-13T18:39:30.169000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-104817"
    }
  }
}

published 2026-10-13 19:29Z
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.

Protected by reCAPTCHA; the Google Privacy Policy and Terms of Service apply.