CVE-2026-14621: FederatedAI FATE · Exposure of Data Element to Wrong Session
Affects FederatedAI FATESource CVE Database V5
Public exploit available · CVSS 2.3 Low.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 4 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| FederatedAIFATE | Affected
| Fixed in– |
GitHubfederatedai/FATEpkg:github/federatedai/FATEOther threats | Affected
| Fixed in– |
CPE configurations (1)
cpe:2.3:a:federatedai:fate:*:*:*:*:*:*:*:*
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A pull request addressing the issue is pending acceptance. Users should monitor the vendor's advisories for the official patch release. Until then, no specific mitigation actions are documented. Given the low severity and high complexity, immediate urgent action is not required.
Description
A vulnerability has been found in FederatedAI FATE up to 2.2.0. This affects the function QueuePushReqStreamObserver.initEggroll of the file java/osx/osx-broker/src/main/java/org/fedai/osx/broker/grpc/QueuePushReqStreamObserver.java of the component OSX Broker. Such manipulation of the argument rollSiteSessionId/dstRole/dstPartyId leads to exposure of data element to wrong session. The attack can be executed remotely. A high complexity level is associated with this attack. It is indicated that the exploitability is difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.
References
- vuldb.com/vuln/376137 (opens in a new tab)
- vuldb.com/vuln/376137/cti (opens in a new tab)
- vuldb.com/cve/CVE-2026-14621 (opens in a new tab)
- vuldb.com/submit/844900 (opens in a new tab)
- github.com/FederatedAI/FATE/issues/5791 (opens in a new tab)
- github.com/FederatedAI/FATE/pull/5792 (opens in a new tab)
- github.com/FederatedAI/FATE/ (opens in a new tab)