Documented CVEs
13 vulnerabilities cataloged in the Hermes intelligence repository.
mcp-atlassian (Model Context Protocol) — Security Intelligence & Vulnerability Profile
1. Software Identity & Security Posture
Section titled “1. Software Identity & Security Posture”| Parameter | Technical Specification |
|---|---|
| Official Name | mcp-atlassian (Model Context Protocol) |
| Vendor / Project | sooperset |
| Canonical ID | sooperset:mcp_atlassian |
| Versioning Scheme | semver |
| CPE Identifiers | cpe:2.3:a:sooperset:mcp_atlassian:*:*:*:*:*:*:*:* |
| Overall Posture | CRITICAL |
| Recommended Safe Release | 0.22.0 |
CISA KEV Entries
4 flaws with confirmed active in-the-wild exploitation.
Weaponized Exploits
12 vulnerabilities with publicly available PoCs or weaponized exploit tooling.
Remediation Target
Recommended upgrade to 0.22.0 to neutralize known flaws.
2. 30-Day Risk Trajectory & Trend Evolution
Section titled “2. 30-Day Risk Trajectory & Trend Evolution”Progression of Hermes Threat Score (HTS) posture and maximum EPSS probability over the last 30 days:
Current HTS Score
0 / 100
= Stable over 30d
Max EPSS (Exploitation)
45.0 %
= Stable over 30d
CISA KEV Activity
0
No active KEV
HTS Trend Curve (D-30 → Today)2026-08-12 → 2026-09-10
3. Vulnerability History & Version Applicability Matrix
Section titled “3. Vulnerability History & Version Applicability Matrix”| CVE | CVSS Score | EPSS Probability | CISA KEV | Affected Versions | Fixed In | Hermes Analysis |
|---|---|---|---|---|---|---|
| CVE-2026-77254 | 9.1 (CRITICAL) | 45.0% | CISA KEV | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-27825 | 9.1 (CRITICAL) | 45.0% | CISA KEV | < v0.17.0 | 0.17.0 | Analysis → |
| CVE-2026-77248 | 8.6 (HIGH) | 45.0% | CISA KEV | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77257 | 8.3 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77267 | 8.2 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-27826 | 8.2 (HIGH) | 45.0% | CISA KEV | < v0.17.0 | 0.17.0 | Analysis → |
| CVE-2026-77266 | 8.1 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77269 | 7.8 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77270 | 7.8 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-73498 | 7.7 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77258 | 7.7 (HIGH) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77272 | 6.1 (MEDIUM) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
| CVE-2026-77268 | 5.5 (MEDIUM) | 15.0% | No | < v0.22.0 | 0.22.0 | Analysis → |
4. Ransomware & Threat Actor Exposure
Section titled “4. Ransomware & Threat Actor Exposure”Vulnerabilities impacting mcp-atlassian (Model Context Protocol) are actively leveraged in real-world intrusion campaigns:
- CVE-2026-77254: Unknown (Read deep dive analysis)
- CVE-2026-27825: Unknown (Read deep dive analysis)
- CVE-2026-77248: Unknown (Read deep dive analysis)
- CVE-2026-27826: Unknown (Read deep dive analysis)
5. Evaluate Running Versions in Interactive Workbench
Section titled “5. Evaluate Running Versions in Interactive Workbench”Are you operating mcp-atlassian (Model Context Protocol) in your infrastructure? Inspect your running build to evaluate applicability, confidence score, and security deltas:
Launch Software Intelligence Workbench for mcp-atlassian (Model Context Protocol) Run deterministic in-browser evaluation, calculate HTS threat reduction, and plan your upgrade path.