Trending Topics
Critical QNAP QVR Pro Flaw Opens Door to Remote Intrusion
QNAP has issued an urgent security advisory for CVE-2026-22898, a critical vulnerability in its QVR Pro network video surveillance platform that allows remote attackers to gain system access without authentication. Tracked as ZDI-CAN-28327 and tied to advisory QSA-26-07, the flaw stems from a missing authentication check on a sensitive QVR Pro function, enabling anyone on the network or internet (depending on exposure) to send crafted requests and interact directly with the core system, no valid username or password required. Systems running QVR Pro 2.7.x prior to 2.7.4.14 (packaged by QNAP as 2.7.4.1485 and later) are affected, and the CVSS 4.0 score of 9.3 reflects the high impact on confidentiality, integrity, and availability. The risk extends well beyond a single surveillance application instance. Once exploited, an attacker could silently view live camera feeds, alter or disable cameras, and wipe recordings to conceal physical or cyber incidents, undermining both security and regulatory obligations. Because QVR Pro typically runs on QNAP NAS devices that also store business-critical data and sit inside core network segments, a compromised QVR Pro host becomes an ideal foothold for lateral movement, data theft, and ransomware deployment across the broader environment. QNAP notes the issue was responsibly reported by FuzzingLabs researchers, and NVD classifies the bug under CWE-306 (Missing Authentication for Critical Function), placing it squarely in the category of “single-bug, full-system compromise” issues that defenders must prioritize. QNAP has already released a fix and marks the vulnerability as resolved in QVR Pro version 2.7.4.14 and later, urging all customers to update immediately via the QTS or QuTS hero App Center interface. Administrators should confirm that QVR Pro is at least 2.7.4.1485, restrict external exposure of NAS and QVR services, enforce strong admin credentials and MFA where possible, and review logs for unusual access to QVR endpoints or configuration changes during the vulnerable window. Given the attractiveness of internet-exposed NAS for mass exploitation, organizations should also ensure timely firmware updates, network segmentation for surveillance systems, and deployment of intrusion detection controls capable of spotting anomalous requests to QVR Pro APIs.
Trivy Supply Chain Attack Expands as Compromised Docker Images Hit Docker Hub
The Trivy supply chain incident has escalated, with security researchers confirming that additional Trivy images on Docker Hub have been turned into delivery vehicles for credential‑stealing malware linked to TeamPCP. Recently published versions that appeared routine were later found to be tampered with, meaning organizations that pulled what looked like the “latest” Trivy image during this period may have unknowingly deployed malicious code into their build systems and environments. This builds on earlier compromises of Trivy components and suggests the attackers are systematically targeting both the project’s source and its distribution channels. There are also indications that Aqua Security’s broader development environment was compromised, giving attackers the opportunity to manipulate internal projects and multiple downstream release paths simultaneously. That raises the risk from a single incident to a wider ecosystem problem, where trusted automation and security tooling become entry points for attackers. In this context, any affected Trivy versions should be treated as untrusted, and systems that used them should be reviewed as potentially compromised until proven otherwise. For defenders, the practical response is to identify where Trivy is used, roll back to the last known safe release, and rotate any credentials that may have been exposed through compromised images. Teams should also tighten how they manage software supply chains overall: limit the power and lifetime of access tokens, scrutinize unexpected version changes from critical tools, and add oversight so that even trusted security components cannot silently introduce high‑impact malware into pipelines.
CanisterWorm Turns Trusted npm Publishers into a Self-Spreading Supply Chain Worm
CanisterWorm is a new npm supply chain campaign in which the TeamPCP group hijacks real, trusted publisher accounts rather than creating fake, look‑alike packages. Once they steal a valid publishing token or CI/CD access, they push “normal‑looking” new versions that secretly install a backdoor as soon as developers run a routine dependency install. This turns widely used SDKs into silent infection vectors, spreading quickly across every project that depends on them. The campaign uses a decentralized control channel so attackers can change or pause their malware without directly touching infected systems, and it heavily focuses on stealing more npm tokens from compromised developers and build systems. That allows the operation to scale: every newly compromised publisher account becomes a launchpad for backdooring more packages and reaching more organizations. As a result, the blast radius spans multiple companies and toolchains, not just a single library. Defenders are advised to assume compromise if they rely on affected package versions, rotate all npm and CI/CD credentials, and carefully review publish histories for unauthorized releases under their namespaces. They should also remove any suspicious persistence mechanisms, reinstall dependencies from known‑good versions, and tighten future exposure by limiting token scope and lifetime, reviewing dependency changes, and reducing automatic execution of install-time scripts where possible.
