CVE-2026-117544

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

GHSA-c26x-8grc-xmfm ↗EUVD-2026-124616 ↗

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.
jdownloads.com jDownloads extension for Joomla 1.0.0-4.1.7
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
ETK-2026-4308Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 14msince last run
48mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h37m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

jDownloads for Joomla versions earlier than 4.1.8 can fail to apply access controls to a referenced download file. An attacker able to use the download request flow may retrieve a restricted file when a target restricted download exists.

mitigation

Update jDownloads to version 4.1.8 or later. Until updated, restrict access to the download request flow and review exposure of restricted downloads.

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.
–
agent run time
48m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-12 18:07Z
Δ 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, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

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

  1. 2026-11-12 18:07Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-4308",
  "cve_id": "CVE-2026-117544",
  "display_id": "CVE-2026-117544",
  "ghsa_id": "GHSA-c26x-8grc-xmfm",
  "euvd_id": "EUVD-2026-124616",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Insecure direct object reference in jDownloads for Joomla",
  "summary": "jDownloads for Joomla versions earlier than 4.1.8 can fail to apply access controls to a referenced download file. An attacker able to use the download request flow may retrieve a restricted file when a target restricted download exists.",
  "mitigation": "Update jDownloads to version 4.1.8 or later. Until updated, restrict access to the download request flow and review exposure of restricted downloads.",
  "vendor": "jdownloads.com",
  "product": "jDownloads extension for Joomla",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "1.0.0-4.1.7"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "jDownloads extension for Joomla",
      "purl": null
    }
  ],
  "cwes": [
    200
  ],
  "cvss_score": 8.2,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 47.84165281666667,
  "t0_at": "2026-11-12T18:07:41.250000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-12T18:07:41.250000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-12T18:07:41.250000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-117544"
    }
  }
}

published 2026-11-12 19:19Z
last change 2026-11-12 23:56Z

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.