Update command fails with 404: repo projectdiscovery/vulnx not found

[yendpoint]

When running the suggested update command (vulnx --update or vulnx update), the updater attempts to fetch releases from https://api.github.com/repos/projectdiscovery/vulnx/releases/latest, which returns 404 Not Found because the repository projectdiscovery/vulnx does not exist.
Observed output:
[INF] Checking for vulnx updates...
[updater] failed to download latest release got [:RUNTIME] repo projectdiscovery/vulnx not found <- GET https://api.github.com/repos/projectdiscovery/vulnx/releases/latest: 404 Not Found

[bad-antics]

This is a known issue — the self-updater binary name doesn't match the GitHub repository name.

The tool is published as cvemap on GitHub (projectdiscovery/cvemap), but the binary was renamed/aliased to vulnx at some point. The updater is looking for projectdiscovery/vulnx which doesn't exist.

Fix:

1. Update manually using go install:

go install -v github.com/projectdiscovery/cvemap/cmd/cvemap@latest

2. Or use pdtm (ProjectDiscovery Tool Manager) which handles updates correctly:

# Install pdtm first
go install -v github.com/projectdiscovery/pdtm/cmd/pdtm@latest

# Then update cvemap through it
pdtm -update-all
# or specifically
pdtm -install cvemap

3. Or download the latest release directly:

# Linux
curl -sL https://github.com/projectdiscovery/cvemap/releases/latest/download/cvemap_linux_amd64.zip -o cvemap.zip
unzip cvemap.zip
sudo mv cvemap /usr/local/bin/

The root cause is that the binary's internal update mechanism references the wrong repository name. This should be fixed in the source code — the updater config likely has vulnx hardcoded instead of cvemap.