Devotd Github
NewSecurity

hevnsnt/cvengine v1.2.1 — External Attack Surface Assessment Tool

hevnsnt/cvengine is a self-hosted tool that finds exposed assets and services and validates vulnerability information in a read-only fashion.

Repositoryhevnsnt/cvengine ↗

hevnsnt/cvengine is a self-hosted tool that finds exposed assets and services and validates vulnerability information in a read-only fashion.

GitHub description: AI-first external attack surface assessment with continuous discovery, evidence-based vulnerability validation, and developer-agent MCP integration.

stars
★ 427
Forks
66
Language
Python
License
GPL-3.0
Latest release
v1.2.1
Read original source ↗View on GitHub ↗

hevnsnt/cvengine is a self-hosted external attack surface assessment tool that discovers externally exposed assets and services and cross-checks them against known vulnerability information. The latest release listed in the investigation record is v1.2.1, and the repository is hevnsnt/cvengine on GitHub. The provided materials contain no changes for this release, so what differs between versions cannot be confirmed. It is written in Python and uses the GPL-3.0 license.

The flow described in the README runs from asset discovery and service identification through vulnerability information matching, prioritization, read-only validation, and change history tracking. Read-only validation is the procedure of cross-checking vulnerability information against the actual environment without making any change to the target. It operates via Docker Compose and provides a dashboard, an API, notification features, and an MCP server for connecting with developer agents. MCP is the way agents connect to external tools. According to the README, discovery and scanning, matching, and validation can be used without artificial intelligence.

This repository is a fork based on reNgine 2.x. The investigation record finds its novelty in bundling multiple scanners, threat intelligence, and validation procedures into a single self-hosted tool, and assesses that the originality of the implementation requires examining the upstream project and external components together. Therefore, the scope of features and the operational flow can be confirmed, but it is difficult to assert high originality from these materials alone.