cve-impact
**CRITICAL**: Use for ALL CVE discovery and listing. DO NOT call get_cves directly. Use when: "show critical CVEs", "CVEs on hostname X", "remediatable vulnerabilities", "impact of CVE-X", risk assessment. NOT for remediation (use `/remediation`). System-level: FIRST reply = pagination prompt (Step -1). Parsing: references/01-cve-response-parser.py.
55
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./rh-sre/skills/cve-impact/SKILL.mdSecurity
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
W011: Third-party content exposure detected (indirect prompt injection risk)
What this means
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Why it was flagged
Third-party content exposure detected (high risk: 0.75). The required runtime workflow calls Lightspeed MCP tools like `vulnerability__get_system_cves`/`get_cve`, whose JSON includes outsider-authored CVE text fields (e.g., `attributes.description`/`synopsis` from public CVE/NVD/Red Hat CVE database) that are then parsed and rendered into the agent’s LLM context via the report/summary output.
W021: Hidden or invisible Unicode characters detected (potential obfuscation or prompt injection)
Why it was flagged
Hidden Unicode characters detected (1 type(s) found)
- Repository
- RHEcosystemAppEng/agentic-collections
- Commit
27852c0
- Audited
- Security analysis
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.