Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local low-privilege access
-
DeliveryCraft input abusing untrusted security decision
-
ExploitFeed to isSecurityDefenseSkill in context.js
-
ExecutionMisclassify malicious content as trusted
-
ImpactScanner suppresses detection (integrity impact)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Trusted input validation
|
| Exploitation Conditions | Exploitation requires local access (AV:L) with existing low privileges (PR:L) and passive user interaction (UI:P), and the attacker must be able to get crafted input processed by the agentverus-scanner's context analysis path so that the isSecurityDefenseSkill function in dist/scanner/analyzers/context.js evaluates it. The concrete prerequisite is control over the untrusted input that feeds the scanner's security-defense-skill classification decision. Limiting factors: no remote/network vector, an authenticated local foothold is needed, impact is confined to weakening the scanner's own detection (low integrity) with no data disclosure or service impact, and the affected product is a niche tool - so realistic risk is minimal even though public exploit material exists. |
| Impact | This is a genuinely low-priority issue and the low CVSS 4.0 score (2.4) is well-justified rather than deflated. The vector (CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N) shows a purely local vulnerability requiring existing low-privilege access and passive user interaction, with impact limited to a low integrity effect and no confidentiality or availability impact. Public exploit code exists (referenced as GitHub issue #28), which raises attacker convenience, but POC availability is a distinct signal from active exploitation - there is no CISA KEV listing and no EPSS score provided, so there is no evidence of real-world or automated exploitation. The signals are internally consistent: a local-only, integrity-only weakness in a niche developer tool. The CWE (CWE-807, reliance on untrusted inputs in a security decision) matches the described flaw - the scanner's own defense-classification logic can be fooled - meaning the practical consequence is a scanner that under-reports, not a direct system compromise. Net: low real-world risk despite the public POC. |
| Exploit ScenarioDerived | An attacker who can supply input to the agentverus-scanner analysis pipeline (e.g., a crafted agent skill/context the scanner ingests) manipulates data so the isSecurityDefenseSkill function misclassifies malicious content as a legitimate security-defense skill, causing the scanner to skip or downgrade its detection. Public exploit material exists via the project's GitHub issue #28. Because the CVSS vector is local (AV:L) with low privileges and passive user interaction, the attacker needs a foothold or to get their input processed locally rather than exploiting over the network. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 28, 2026
Untrusted input routed into agentverus-scanner's security-defense-skill analyzer can override the classification decision made by isSecurityDefenseSkill in dist/scanner/analyzers/context.js, allowing an attacker to weaken or falsify the scanner's own detection results for versions up to 0.8.1. Exploitation requires an authenticated local foothold and passive user interaction, and the impact is limited to low integrity loss with no confidentiality or availability effect; the CVSS 4.0 score of 2.4 reflects that narrow scope and is appropriately calibrated rather than deflated. Publicly available exploit code exists, and the project was notified via an issue report but has not responded, so no vendor-released patch has been identified at time of analysis.
RemediationAI
No vendor-released patch has been identified at time of analysis, and the upstream issue report at https://github.com/agentverus/agentverus-scanner/issues/28 remains unanswered, so no fixed version can be cited; anyone running 0.8.1 or earlier must mitigate or vendor a fix. The most direct remediation is to patch isSecurityDefenseSkill in dist/scanner/analyzers/context.js so the security-defense determination is derived only from trusted, server-side configuration or a signed allowlist rather than from scanned content, with the trade-off that the analyzer becomes less adaptive and may require allowlist upkeep. Until that fix is available, treat all scanner verdicts as advisory: run the scanner in a sandbox or container with least privilege and no access to production secrets, and require a second independent tool or human review before acting on any security-defense classification the scanner produces - the trade-off being added analyst overhead and slower triage. Restrict who can supply artifacts or context data into the scanner's input path (local, low-privilege accounts already satisfy the PR:L prerequisite, so remove that interaction path where it is not essential) and disable or stub the context-based security-defense-skill heuristic if your deployment does not depend on it, accepting reduced detection coverage in exchange for eliminating the untrusted-input decision. Monitor the GitHub repository and the VulDB entries at https://vuldb.com/vuln/410950 and https://vuldb.com/cve/CVE-2026-101079 for a patched release, and roll it out promptly once published. Note that publicly available exploit code exists for this issue, though it is not confirmed as actively exploited (CISA KEV).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is CWE-807 (Reliance on Untrusted Inputs in a Security Decision) and lives in the analyzer module dist/scanner/analyzers/context.js, specifically in the isSecurityDefenseSkill function. That routine is part of agentverus-scanner's context analysis pipeline: it inspects the context surrounding a scanned artifact to decide whether a skill or component should be treated as a security-defense mechanism, and that boolean decision then shapes downstream reporting and risk classification. Because the function performs its decision using input that the attacker can influence rather than validating, normalizing, or bound-checking it first, a crafted value can steer the branch and produce an incorrect security judgment. The CPE cpe:2.3:a:agentverus:agentverus-scanner:*:*:*:*:*:*:*:* confirms the entire product line through the 0.8.1 release is in scope, and the vulnerable path is the Node.js scanner code shipped in the package's dist directory. This is a decision-integrity weakness internal to the tool, not a memory-safety, injection, or remote-code-execution primitive.
Know when Agentverus Scanner gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N/E:P
Local low-privilege attacker with required user interaction manipulates untrusted input into a security decision, yielding only a low integrity impact (detection bypass) and no confidentiality or availability effect.
Primary rating from Vendor (VulDB).
CVSS VectorVendor: VulDB
Lifecycle Timeline
2DescriptionCVE.org
A vulnerability was found in agentverus agentverus-scanner up to 0.8.1. Affected by this vulnerability is the function isSecurityDefenseSkill of the file dist/scanner/analyzers/context.js. Performing a manipulation results in reliance on untrusted inputs in a security decision. The attack must be initiated from a local position. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
EUVD-2026-88336
GHSA-3prr-pcv3-5chg
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB