CVE-2026-113678

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

GHSA-j3hm-8rm8-m243 ↗EUVD-2026-105094 ↗

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.
froxlor < 2.3.15
fixed in 2.3.15
ETK-2026-2208Zero's internal tracking ID, independent of the CVE number., permanent identifier
10h 45msince last run
28mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h10m
0
+2h
+6h
+8h
+10h
+12h

description

Froxlor versions before 2.3.15 mishandle symbolic links during statistics-related ownership changes. An authenticated customer may cause a privileged scheduled task to alter ownership outside the intended directory, potentially leading to privilege escalation; the root-run traffic cron must be enabled or invoked.

mitigation

Upgrade Froxlor to version 2.3.15 or later. Until upgraded, restrict untrusted customer control over statistics directories and disable or tightly limit the privileged traffic cron where operationally possible.

fixed in 2.3.15

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
28m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-20 15:40Z
Δ 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-20 15:40Z
    ghsa: trigger signal, started the run
  2. 2026-10-20 15:40Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2208",
  "cve_id": "CVE-2026-113678",
  "display_id": "CVE-2026-113678",
  "ghsa_id": "GHSA-j3hm-8rm8-m243",
  "euvd_id": "EUVD-2026-105094",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Symlink following in Froxlor statistics ownership handling",
  "summary": "Froxlor versions before 2.3.15 mishandle symbolic links during statistics-related ownership changes. An authenticated customer may cause a privileged scheduled task to alter ownership outside the intended directory, potentially leading to privilege escalation; the root-run traffic cron must be enabled or invoked.",
  "mitigation": "Upgrade Froxlor to version 2.3.15 or later. Until upgraded, restrict untrusted customer control over statistics directories and disable or tightly limit the privileged traffic cron where operationally possible.",
  "vendor": "froxlor",
  "product": "froxlor",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 2.3.15"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.3.15"
      ],
      "package_name": "froxlor",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.9,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 28.3459808,
  "t0_at": "2026-10-20T15:40:39.663000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-20T15:40:39.663000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-20T15:40:39.663000+00:00",
      "url": "https://github.com/advisories/GHSA-j3hm-8rm8-m243"
    }
  }
}

published 2026-10-20 19:22Z
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.