Is there a public PoC exploit available for CVE-2026-14621?

Yes, a public proof-of-concept exploit is available for CVE-2026-14621. Prioritise patching immediately. EPSS: 0.3%.

Is there a patch available for CVE-2026-14621?

Yes, a patch is available for CVE-2026-14621. Update the affected software to the latest version immediately.

FederatedAI FATE CVE-2026-14621

Q: What is the CVSS score of CVE-2026-14621?

CVE-2026-14621 has a CVSS 4.0 base score of 1.3 (Low). CVSS vector: 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:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-41660 LOW

Exposure of Data Element to Wrong Session (CWE-488)

2026-07-04 VulDB

GHSA-pqmh-9h5r-56pf

Java Information Disclosure Fate

1.3

CVSS 4.0 · Vendor: VulDB

Severity by source

Vendor (VulDB) PRIMARY

1.3 LOW

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:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

3.1 LOW

Network-reachable gRPC endpoint requires authenticated federated party (PR:L); high complexity to forge valid cross-session identifiers; only limited confidentiality exposure, no integrity or availability impact.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

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

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Jul 04, 2026 - 09:22 NVD

2.3 (LOW) 1.3 (LOW)

Analysis Generated

Jul 04, 2026 - 09:01 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Session data exposure in FederatedAI FATE's OSX Broker gRPC component allows an authenticated federated party to manipulate session routing arguments and access data belonging to a different federated session. Affected versions extend through FATE 2.2.0, specifically in the QueuePushReqStreamObserver.initEggroll method within the Java-based OSX Broker. No public exploit confirmed active exploitation (not in CISA KEV), though exploit code has been publicly disclosed via a GitHub issue, and the CVSS 4.0 score of 2.3 reflects the high attack complexity and limited confidentiality impact.

Technical ContextAI

FATE (Federated AI Technology Enabler) is an open-source federated learning framework developed by WeBank under the FederatedAI project. The OSX Broker component mediates gRPC streaming communication between federated learning parties using the Eggroll runtime. The vulnerable function QueuePushReqStreamObserver.initEggroll, located at java/osx/osx-broker/src/main/java/org/fedai/osx/broker/grpc/QueuePushReqStreamObserver.java, fails to properly isolate session-scoped data. CWE-488 (Exposure of Data Element to Wrong Session) identifies the root cause: the arguments rollSiteSessionId, dstRole, and dstPartyId can be crafted or manipulated by a caller to redirect session context, causing the broker to expose data from one federated session to a requester belonging to a different session. The affected CPE is cpe:2.3:a:federatedai:fate:*:*:*:*:*:*:*:* for all versions up to and including 2.2.0.

RemediationAI

The upstream fix is available as GitHub Pull Request #5792 (https://github.com/FederatedAI/FATE/pull/5792), but at time of analysis this PR had not yet been accepted and merged, meaning no officially released patched version has been independently confirmed. Organizations should monitor the FATE repository for a tagged release incorporating this fix and upgrade promptly when available. As an interim compensating control, operators should restrict network access to the OSX Broker gRPC endpoint to only trusted, explicitly authorized federated parties using network-level access controls or mTLS enforcement, reducing the pool of potential attackers to those with legitimate party credentials. Additionally, reviewing and enforcing strict session identifier validation at the network perimeter or via FATE's own party authentication mechanisms can limit the ability to supply forged rollSiteSessionId, dstRole, or dstPartyId values. Note that network restriction may impact federated training workflows that rely on dynamic party connectivity.