Skip to main content
Menu
CVEs

Gladys Assistant path traversal in Backup Restore exposes files

CVE-2026-133501EUVD-2026-131366GHSA-FWGC-XCGM-2J42Published , updated

9.4CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

A path traversal flaw in the Backup Restore component of Gladys Assistant lets an attacker reach files outside the intended directory. The attacker can reach it remotely over the network with low-level login access, and it requires some action from a user.

Written by a model

Original description

A security flaw has been discovered in Gladys Assistant up to 4.71.0. This impacts an unknown function of the file server/lib/gateway/gateway.downloadBackup.js of the component Backup Restore Handler. The manipulation results in path traversal. The attack can be launched remotely. The exploit has been released to the public and may be used for attacks. Upgrading to version 4.72.0 will fix this issue. It is recommended to upgrade the affected component.

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-133501 (Gladys Assistant Backup Restore gateway.downloadBackup.js path traversal), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-133501 (entry last updated 2026-11-20):
Affected:
- n/a Gladys Assistant: versions 4.0, 4.1, 4.2, 4.3, 4.4, 4.5, 4.6, 4.7, 4.8, 4.9, 4.10, 4.11 and 60 more
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133501 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133501 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/GladysAssistant/Gladys/releases/tag/v4.72.0
- https://vuldb.com/vuln/440923
- https://vuldb.com/vuln/440923/cti
- https://vuldb.com/cve/CVE-2026-133501
- https://vuldb.com/submit/1049319
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-133501
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133501"}.

Affected versions

cve.now Index

28Pof 100 · provisional · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  4. Record last updated
  5. Posted on X by cve.now

Evidence 8

KindSource
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-133501
RecordNVD · CVE-2026-133501
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · GladysAssistant/Gladys · Issue #2495
Other links 5
AdvisoryVulDB · Advisory #440923
AdvisoryVulDB · Threat intelligence #440923
AdvisoryVulDB · CVE-2026-133501 record
AdvisoryVulDB · Submission #1049319
PatchGitHub · GladysAssistant/Gladys · Release v4.72.0

Questions about CVE-2026-133501

Is CVE-2026-133501 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133501?

Gladys Assistant: versions 4.0, 4.1, 4.2, 4.3, 4.4 and 67 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.