Loading vulnerability…
CVE-2025-27580 affects NIH BRICS (Biomedical Research Informatics Computing System) through version 14.0.0-67. The application generates tokens using predictable inputs: the username, the time, and a fixed hard-coded string ("7Dl9#dj-"). Because the token generation mechanism is deterministic and based on low-entropy, guessable values plus a static secret, an attacker can predict or reproduce valid tokens. The issue enables an unauthenticated user who possesses a Common Access Card (CAC) to forge or derive tokens associated with other users and thereby compromise arbitrary accounts, including administrator accounts.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit for CVE-2025-27580, a vulnerability in NIH BRICS (Biomedical Research Informatics Computing System) through version 14.0.0-67. The exploit demonstrates how an unauthenticated attacker can generate valid authentication tokens for any user, including administrators, by leveraging a predictable token generation scheme that uses a known salt ('7Dl9#dj-'), a username, and a timestamp. The repository consists of two files: a README.md describing the vulnerability and a Python script (exploit.py) that implements the token generation logic. The exploit is a POC and does not include code to interact directly with the NIH BRICS system, but it provides the core logic needed to forge authentication tokens for account takeover attacks. The main attack vector is network-based, as the attacker would use the generated token to authenticate to the target system.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.