cve.bz

CVE-2026-127090 Jadaptive Maverick Synergy Server before 3.0.33 and 3.1.x before 3.1.7, and Maverick Legacy Server before 1.8.1, SSH Public Key Cross-User Authentication Bypass

8.7 highEPSS 0.8%

High (8.7) in jadaptive. EPSS 0.8% estimated probability of exploitation activity in the next 30 days.

On this page
Jadaptive Maverick Synergy Server before 3.0.33 and 3.1.x before 3.1.7, and Maverick Legacy Server before 1.8.1, contain an authentication bypass vulnerability in SSH public key authentication that reuses cached key authorization decisions across usernames. Attackers holding a key authorized for one account can authenticate it, then send a signed SSH_MSG_USERAUTH_REQUEST with a different username on the same connection to log in as that account.

Severity

CVSS 4.0

8.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.8% estimated probability of exploitation activity in the next 30 days; 56th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-13. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-305 Authentication Bypass by Primary Weakness
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
Assigned by
VulnCheck (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-127090 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-127090?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-127090?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-127090 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-127090

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-127090](https://cve.bz/cve/badge/CVE-2026-127090.svg)](https://cve.bz/cve/CVE-2026-127090)

HTML:

<a href="https://cve.bz/cve/CVE-2026-127090"><img src="https://cve.bz/cve/badge/CVE-2026-127090.svg" alt="CVE-2026-127090"></a>

Affected

  • jadaptive:maverick legacy server
  • jadaptive:maverick synergy server

Versions

From the CNA's record in the CVE List.

ProductAffected
Jadaptive Maverick Synergy Serverbefore 3.0.33
Jadaptive Maverick Synergy Serverfrom 3.1.0 before 3.1.7
Jadaptive Maverick Legacy Serverbefore 1.8.1

References

Check your stackJSON