Skip to main content
Menu
CVEs

Gladys Assistant remote OS command execution in backup restore endpoint

CVE-2026-133500Published , updated

9.4CriticalCNA
Exploited
No known exploitation
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

Gladys Assistant has an OS command injection flaw in its backup restore endpoint, where the file_url argument is not handled safely. An attacker with high-level privileges can reach it remotely over the network and run operating system commands on the host.

Written by a model

Original description

A vulnerability was identified in Gladys Assistant up to 4.71.0. This affects an unknown function of the file gateway.downloadBackup.js of the component Backup Restore Endpoint. The manipulation of the argument file_url leads to os command injection. The attack can be initiated remotely. The exploit is publicly available and might be used. Upgrading to version 4.72.0 mitigates this issue. Upgrading the affected component is recommended.

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-133500 (Gladys Assistant Backup Restore Endpoint gateway.downloadBackup.js os command injection), 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-133500 (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-133500 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133500 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/440922
- https://vuldb.com/vuln/440922/cti
- https://vuldb.com/cve/CVE-2026-133500
- https://vuldb.com/submit/1049318
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-133500
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-133500"}.

Affected versions

cve.now Index

12Pof 100 · provisional · methodology v3
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.4/10CVSS 9.4
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 31 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now

Evidence 8

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

Questions about CVE-2026-133500

Is CVE-2026-133500 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. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-133500?

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.