CVSS
Common Vulnerability Scoring System · CVSS score
The Common Vulnerability Scoring System, a 0 to 10 severity score for a vulnerability; 7.0 and above is high, 9.0 and above critical.
In our briefings
What our briefings say about CVSS itself, with the most direct claims first.
OWASP's AIVSS v0.8 starts from a CVSS v4.0 base score and adds an uplift worth part of the gap between that base and 10. Ten agentic factors, each scored 0, 0.5 or 1, set the share, and an exploit-maturity multiplier scales it, by default 0.97. With the default mitigation factor of 1.0 (no or weak mitigation), all ten worked examples in the document land between 7.1 and 10.0, seven Critical and three High, and a goal-manipulation flaw with a CVSS base of 2.1 comes out at 7.1. The authors read a jump like that as a sign that the agentic deployment context, not the technical flaw, is the main risk driver. On our reading of the formula, a score can only fall below its CVSS base through the mitigation factor, and the document warns that AIVSS scores are not directly comparable to CVSS base scores.
OWASP's AIVSS lifts a CVSS 2.1 agent flaw to 7.1, and all ten worked examples land High or CriticalBI-FIND-2026-2299
Both of Bifrost's critical flaws came from its management API shipping with authentication disabled by default and its official Docker image binding that API to 0.0.0.0. In CVE-2026-90898 (CVSS 9.8, disclosed by JFrog on 14 September 2026), one unauthenticated POST to /api/mcp/client registered a stdio MCP client, and the gateway started the named command at once, before any MCP handshake, as its own process user. CVE-2026-86242 (CVSS 8.1, 6 September) let an unauthenticated caller register a custom plugin, which the gateway downloaded and ran as a shared object with full process privileges. The plugin flaw was fixed in 2.0.0; version 2.1.0 closes the MCP one by requiring a setup token before anyone can claim the first admin account. The post's headline blames MCP's lack of client authentication, but its body concedes "there was no protocol gap to close": on a gateway that accepts local servers, "Registration and execution are the same event", and the admin surface where that happens is one the MCP specification does not describe.
Registering an MCP server on Bifrost ran its command, and the admin API that allowed it shipped with no passwordBI-FIND-2026-0481
›Cited in 7 briefings
Every briefing that discusses this term, newest first.
- One uploaded document gave a researcher interactive access to a victim's Copilot
Video · · Black Hat · Uploaded November 13, 2026
- Can your identity stack be patched for AI agents, or does it have to be replaced? NewCore's CTO says replaced
Podcast · · TechSpective Podcast · Rebuilding Identity Security From Scratch for the Age of AI Agents · Sep 21, 2026
- OWASP's AIVSS lifts a CVSS 2.1 agent flaw to 7.1, and all ten worked examples land High or Critical
Article · · OWASP AIVSS project · Ken Huang et al. · Oct 22, 2026
- Visa’s agent-written patches still need human acceptance and attack-path validation
Podcast · · AI Security Podcast · How Visa Secures Trillions Using AI Agents & Open-Source Harnesses · Oct 2, 2026
- Registering an MCP server on Bifrost ran its command, and the admin API that allowed it shipped with no password
Article · · WorkOS Blog · Maria Paktiti · Sep 29, 2026
- Three MCP auth flaws reached public attention in one month, each from trusting input nobody verified
Article · · WorkOS Blog · Maria Paktiti · Oct 2, 2026
- A 'zero trust' registry against AI tool squatting still has to trust its administrator
Paper · · arXiv · Vineeth Sai Narajala et al. · Apr 28, 2025