Vulnaware Bridges Vulnerability Scanners and ITSM Systems to Improve Critical Flaw Prioritization
A Russian security engineer has released Vulnaware, an open-source prioritization engine designed to solve one of the most persistent problems in vulnerability management: ensuring that genuinely dangerous flaws reach remediation teams before they become incidents.
The project was created after the author observed that vulnerabilities rarely compete successfully for attention inside IT service desks because they lack an associated ticket, SLA, or downtime impact. According to Verizon DBIR 2026, exploitation of vulnerabilities overtook credential theft for the first time in the report’s 19-year history, accounting for 31 percent of breaches compared with 20 percent the previous year.
Vulnaware is not a vulnerability scanner or a full VM platform. Instead, it functions as an independent layer that sits between existing scanners and ITSM systems. It currently accepts data from MaxPatrol VM, Nessus Pro, and Greenbone/OpenVAS. Scope is limited at ingestion using asset groups, scan folders, or host tags so that only relevant assets are processed.
Prioritization relies on three concrete signals: presence in the CISA KEV catalog, availability of exploits in community feeds from Vulncheck, and trend indicators when available from MaxPatrol. The goal is to surface only those vulnerabilities that have at least one working exploit, dramatically reducing noise for security and IT teams.
Once an issue is prioritized, Vulnaware can automatically create tickets in Jira Service Management, GLPI, Znuny, and osTicket. It also sends notifications through a Telegram bot (with optional asset obfuscation) and email templates built with Jinja. A lightweight web interface allows manual review and one-click dispatch when automatic routing is not desired.
The tool’s design follows the five-stage lifecycle described in NIST SP 800-40 Rev. 4 and the risk-based timelines introduced by CISA BOD 26-04, which replaced rigid deadlines with a matrix considering asset exposure, KEV listing, exploit automation, and technical impact. By converting prioritized vulnerabilities into properly classified service requests or changes, the solution gives organizations measurable MTTR data for the flaws that actually matter.
Related articles
Six Months After tun0 Leak: Which Android VPN Clients Fixed Server Address Exposure and Which Ignored It
A detailed investigation reveals that Android VPN clients suffer from two distinct server address leaks when split tunneling is enabled. The first leak, tied to an unprotected local SOCKS proxy on 127.0.0.1, was quickly mitigated by most Xray and sing-box based clients through random ports and passwords. The second, more persistent leak allows excluded applications to bind sockets directly to the tun0 interface and discover the VPN server IP without root or special permissions. Only TeapodStream and OlConnect implemented owner-UID checks using ConnectivityManager.getConnectionOwnerUid, yet both initially mishandled the INVALID_UID response returned for excluded apps. AmneziaVPN has unmerged pull requests that correctly reject unknown owners, while sing-box offers a manual package_name_regex rule. v2rayNG closed the report as not planned, and major clients including WireGuard for Android, Mullvad, Proton VPN and others have issued no statements.
Part 2: How Third-Party Developers Closed the tun0 Leak in AmneziaVPN on Android
Third-party contributors to AmneziaVPN have detailed their fix for a VPN tunnel bypass affecting excluded applications on Android. The vulnerability allows any app, even those disallowed from the VPN, to bind sockets directly to the tun0 interface using SO_BINDTODEVICE and thereby discover the VPN server address. The team implemented a packet filter inside the client that queries Android via ConnectivityManager.getConnectionOwnerUid to determine packet ownership and drops traffic from unknown UIDs. The solution was integrated into both the Xray and AmneziaWG traffic paths, with the AmneziaWG hook placed inside amneziawg-go after packet parsing. Testing with leak_probe.py showed zero successful bypass attempts out of six methods when the filter was active, compared to six out of six without it. The developers submitted three pull requests and released a side-loaded test build, while noting remaining limitations such as raw sockets and tethering scenarios.
Cisco Confirms Active Exploitation of CVE-2026-76504 in Catalyst SD-WAN Manager
Cisco has confirmed that the critical vulnerability CVE-2026-76504 in Catalyst SD-WAN Manager has been exploited in attacks throughout September. The flaw carries a CVSS score of 9.8 and allows attackers to gain full administrator access without any credentials by bypassing API authentication through malformed URI encoding. The issue affects the login session handling mechanism, enabling forged requests to grant netadmin privileges by default. Similar URI manipulation techniques were observed earlier this month in Oracle PeopleSoft attacks. Patches are available across multiple release trains including 20.9.10.1, 20.12.8.2, 20.15.6.1, 20.18.4.1, 26.1.2.1 and 26.2.1, while older installations must migrate to supported versions. Cisco recommends restricting access to trusted hosts and placing the Manager behind firewalls until updates are applied. The vulnerability was discovered during routine support operations and verified by Cisco's Product Security Incident Response Team.
Zero-Days in PaperCut MF Chained to Compromise Active Directory in Education Sector
Analysts at eSentire investigated an attack that chained two zero-days in PaperCut MF, tracked as CVE-2026-81578 and CVE-2026-82078, to move from an internet-exposed print server to a domain controller in an education sector client in under two days. Attackers gained initial access through the card or badge query field, delivering malicious Java code that allowed unauthenticated configuration changes and arbitrary bytecode execution on version 24.0.2. The first stage loader reassembled payload fragments in memory, launched the next stage, and deleted its own files while remaining compatible with multiple Tomcat versions. A web shell followed, accepting commands via a custom HTTP header, reading configurations, and erasing log traces while positioning itself early in the request processing chain. The command-and-control implant was AdaptixC2, hidden inside a modified Microsoft Copilot binary downloaded from Alibaba Cloud infrastructure. Privilege escalation was achieved without passwords by locating a domain-privileged service account, stealing its access token, and relaunching the implant under those rights. On the domain controller the payload arrived via administrative share and was executed by modifying the Windows PlugPlay service, after which the legitimate path was restored to minimize traces. The operators extracted credentials from memory and registry, enabled Restricted Admin mode, used an NTLM hash for RDP access, and copied the full Active Directory database containing passwords for all domain accounts.