vuls · Issues· 92 open
Open on GitHubLocally synced open issues (discussions stay on GitHub)
- #777
Support CISCO CVRF repository
Updated Sep 8, 2026 - #2645
Ubuntu: CVEs fixed by an installed ESM (esm-apps/esm-infra) build are still reported as notFixedYet/needed (plain <release> segment wins over esm-apps/<release>)
Updated Aug 21, 2026 - #2557
checkrestart in debian 13 trixie misreports deleted files causing the vuls function to fail
bugUpdated Jun 24, 2026 - #2578
SrcPackages collapses multiple source versions of one source package, causing false negatives/positives
Updated Jun 22, 2026 - #2579
Security: Vulnerability remediation request for Go dependencies and Go runtime (x/crypto, x/net, x/sys, stdlib)
Updated Jun 19, 2026 - #1513
Potentially bad TLS connection settings
DiscussionUpdated May 25, 2026 - #2561
[feature] mcp and to agentic tools mode
enhancementUpdated May 20, 2026 - #2528
macOS scanning via CPE-only detection produces near 100% false positives - is this expected or am I missing configuration?
questionUpdated Apr 27, 2026 - #2486
Move S3, Azure Blob, and Slack reporters to contrib/ as separate modules
Updated Mar 24, 2026 - #2485
Remove WPScan API vulnerability detection (detector/wordpress.go)
Updated Mar 24, 2026 - #2479
fix: merge go.sum into go.mod for Go <1.17 projects
Updated Mar 19, 2026 - #2455
Question: Inconsistent CPE handling across FilterUnfixed / PatchStatus / FormatFixedStatus
Updated Mar 12, 2026 - #2423
scanner cannot manage same-named packages across different architectures or versions
bugUpdated Feb 20, 2026 - #2336
Vuls Server Support for Network Devices
enhancementUpdated Oct 10, 2025 - #2199
Support for Slackware Linux
enhancementUpdated May 7, 2025