CVE-2026-115932

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

GHSA-rmc2-p2gv-m88f ↗EUVD-2026-109293 ↗

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.
GitroomHQ postiz-app >= 2.23.0, < 2.25.3
fixed in 2.25.3
ETK-2026-2551Zero's internal tracking ID, independent of the CVE number., permanent identifier
6h 01msince last run
20mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+4h48m
0
+2h
+4h
+6h
+8h
+10h
+12h

description

Postiz media processing can resolve user-controlled file references outside the intended upload storage. A user who can register or otherwise authenticate may expose files readable by the service through publishing workflows, and related requests may also consume excessive memory. Open self-registration can make the required access easy to obtain.

mitigation

Upgrade postiz-app to 2.25.3 or later.

fixed in 2.25.3

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
20m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-24 12:28Z
Δ 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-24 12:28Z
    ghsa: trigger signal, started the run
  2. 2026-10-24 12:28Z

this entry in the feed

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

{
  "etk_id": "ETK-2026-2551",
  "cve_id": "CVE-2026-115932",
  "display_id": "CVE-2026-115932",
  "ghsa_id": "GHSA-rmc2-p2gv-m88f",
  "euvd_id": "EUVD-2026-109293",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Arbitrary file read through path traversal in postiz-app",
  "summary": "Postiz media processing can resolve user-controlled file references outside the intended upload storage. A user who can register or otherwise authenticate may expose files readable by the service through publishing workflows, and related requests may also consume excessive memory. Open self-registration can make the required access easy to obtain.",
  "mitigation": "Upgrade postiz-app to 2.25.3 or later.",
  "vendor": "GitroomHQ",
  "product": "postiz-app",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 2.23.0, < 2.25.3"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "2.25.3"
      ],
      "package_name": "postiz-app",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 9.6,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 20.198681766666667,
  "t0_at": "2026-10-24T12:28:36.033000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-24T12:28:36.033000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-24T12:28:36.033000+00:00",
      "url": "https://github.com/advisories/GHSA-rmc2-p2gv-m88f"
    }
  }
}

published 2026-10-24 16:56Z
last change 2026-10-24 23:06Z

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.