CVE-2026-33879
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedFederated Learning and Interoperability Platform (FLIP) is an open-source platform for federated training and evaluation of medical imaging AI models across healthcare institutions. The FLIP login page in versions 0.1.1 and prior has no rate limiting or CAPTCHA, enabling brute-force and credential-stuffing attacks. FLIP users are external to the organization, increasing credential reuse risk. As of time of publication, it is unclear if a patch is available.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe FLIP federated learning platform login page in version 0.1.1 and prior lacks rate limiting and CAPTCHA controls, allowing attackers to perform unlimited login attempts. This enables brute-force attacks against known usernames and credential-stuffing attacks using leaked credentials from other breaches. The vulnerability is exacerbated by external users who often reuse passwords across services.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 0.1.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FLIP installationLocate the Aicentre Federated Learning And Interoperability Platform installation in your environment. Check for the application running on your servers or containers, and note the deployment path or service name.Affected if The platform is deployed and the login interface is accessible to users or attackers.
-
Determine installed FLIP versionQuery the installed package or application for its version number. This may be found in the application metadata, about page, or by checking the deployed software artifacts against version 0.1.1.Affected if The installed version is 0.1.1 or any version prior to 0.1.1.
-
Locate the login endpointIdentify the URL or network path to the FLIP login page. This is typically found in the application's routing configuration or documented login URL.Affected if The login page is reachable over the network.
-
Test for rate limiting on loginSend multiple sequential login requests to the identified login endpoint using a script or tool. Observe whether the application imposes any delays, blocks requests, or returns rate-limiting errors after a certain number of attempts.Affected if The application allows unlimited login attempts without any throttling, delays, or account lockouts.
-
Verify CAPTCHA presenceInspect the login page HTML and form submission to determine whether a CAPTCHA challenge is present, especially after failed login attempts. Check if any CAPTCHA component is rendered or triggered.Affected if No CAPTCHA is implemented on the login page, or it is not enforced after failed attempts.
You are affected if FLIP version 0.1.1 or prior is running, the login page is accessible, and neither rate limiting nor CAPTCHA protection is configured on the login endpoint.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data0.1.1
Implement rate limiting on the login endpoint to restrict failed attempts per time window, and consider adding CAPTCHA to further mitigate automated attacks. Enforce multi-factor authentication for external users.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-33879 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-33879 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data