Urgent.News

What's breaking now, across thousands of outlets.

Tech

AhsayCBS CVE-2026-105133 and CVE-2026-105134: The Backup Server as an Attack Platform

AhsayCBS CVE-2026-105133 and CVE-2026-105134: The Backup Server as an Attack Platform Backup software occupies an awkward position in enterprise security. It holds copies of everything, it must reach every system it protects, and its availability is treated as a business-continuity requirement rather than a security surface. Two Ahsay Cloud Backup Suite vulnerabilities exploited in October 2026…

Two vulnerabilities in the Ahsay Cloud Backup Suite, CVE-2026-105134 and CVE-2026-105133, allow attackers to execute commands on the backup server without authentication. The vulnerabilities, reported in October 2026, are rated with CVSS scores of 10.0 and 7.3, respectively. Both vulnerabilities share a parameter name and exploit the backup server's accessibility and availability as a business requirement.

The first vulnerability is an authentication defect, while the second is a command injection. These flaws were added to the Known Exploited Vulnerabilities catalog by CISA, with a federal remediation deadline of October 17, 2026. Ahsay released hotfixes to address the vulnerabilities, but the first hotfix was later found to be incomplete.

Organizations that patched early and removed the issue from their tracking lists may still be vulnerable. Compromised hosts have been observed to deploy web shells and install cryptocurrency miners, such as XMRig. The combination of a web shell and a cryptocurrency miner indicates that attackers aim for both persistence and immediate revenue.

A backup server with a web shell can be used for data exfiltration, altering retention, deleting recovery points, and accessing stored credentials. Mining malware on an internet-facing server within a trusted network segment should be treated as evidence of successful unauthenticated command execution. Practical verification steps include checking the exact Ahsay build, searching for web shell artifacts, checking for miner processes, reviewing backup job history for configuration changes, and testing recent recovery points.

Organizations should consider putting the backup server on a management segment, restricting inbound access to the agent population, and treating its administrative interface like a domain controller's.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Two layers, one browser: why consistency beats any single fingerprint

Most anti-detect tooling still optimizes the wrong objective: it treats fingerprinting as a collection problem, enumerate every readable property, then make each one plausible.

  • JavaScript layer easily spoofed, but network/TLS layer reveals true machine identity
  • Defenders lack information to maintain consistency, making spoofing detection possible

A pre-launch security checklist for apps built with Lovable, Bolt and Cursor

You built an app over a weekend with Lovable, Bolt, Replit or Cursor. It works, the demo looks great, and you are about to share the link. Before you do, spend an hour on the boring stuff.

  • Search for secrets in the front end, replace found secrets and move calls to server functions
  • Test database security from outside with Row Level Security (RLS) and strict policies
  • Configure auth settings to use real domain, test password resets and confirmations

More from Sunday 25 October →