CVE-2026-116067

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

GHSA-c69r-vcvw-qgm3 ↗EUVD-2026-109381 ↗

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.
ananthakumaran paisa < 0.7.8
fixed in 0.7.8
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
ETK-2026-2596Zero's internal tracking ID, independent of the CVE number., permanent identifier
5h 13msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+0h22m
+2h
+4h
+6h
+8h
+10h
+12h

description

Paisa versions before 0.7.8 are affected by path traversal in file and backup handling endpoints. An unauthenticated attacker can read files accessible to the server or delete backup files outside the intended journal or sheets directories by supplying crafted file names.

mitigation

Upgrade paisa to version 0.7.8 or later. Restrict access to the affected editor and backup endpoints until the update is applied.

fixed in 0.7.8

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.
–
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
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-25 11:50Z
Δ 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

No artifact: an exploit or check was attempted but could not be produced at this moment.

source signals

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

  1. 2026-10-25 11:50Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-2596",
  "cve_id": "CVE-2026-116067",
  "display_id": "CVE-2026-116067",
  "ghsa_id": "GHSA-c69r-vcvw-qgm3",
  "euvd_id": "EUVD-2026-109381",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Path traversal in Paisa file and backup handlers",
  "summary": "Paisa versions before 0.7.8 are affected by path traversal in file and backup handling endpoints. An unauthenticated attacker can read files accessible to the server or delete backup files outside the intended journal or sheets directories by supplying crafted file names.",
  "mitigation": "Upgrade paisa to version 0.7.8 or later. Restrict access to the affected editor and backup endpoints until the update is applied.",
  "vendor": "ananthakumaran",
  "product": "paisa",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, < 0.7.8"
      ],
      "ecosystem": null,
      "fixed_versions": [
        "0.7.8"
      ],
      "package_name": "paisa",
      "purl": null
    }
  ],
  "cwes": [
    22
  ],
  "cvss_score": 8.8,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:L/VA:N/SC:N/SI:N/SA:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "deterministic",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 15.681651916666667,
  "t0_at": "2026-10-25T11:50:56.480000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-25T11:50:56.480000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-25T11:50:56.480000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-116067"
    }
  }
}

published 2026-10-25 11:57Z
last change 2026-10-25 17:16Z

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.