CERT Polska disclosed two missing authorization vulnerabilities in MWDB Core that were fixed in version 2.19.0. CVE-2026-66723 affects versions 2.2.0 through before 2.19.0 and allows an unauthenticated attacker to abuse the Remote Instances proxy API to send arbitrary requests to a remote MWDB instance using the configured API key’s identity and permissions. The issue is limited to deployments where Remote Instances are enabled.
CERT Polska also reported CVE-2026-66724, affecting versions 2.0.0 through before 2.19.0, which lets any authenticated user bypass capability checks on deprecated config and blob upload endpoints by using an undocumented POST method. The flaw is limited to unauthorized addition of config and text blob objects. Both issues were classified as CWE-862: Missing Authorization, underscoring authorization control failures that could let attackers act beyond intended privileges.

See affected versions and whether adversaries are exploiting it.
1 event from the most recent confirmed update back to the earliest known activity.
CERT Polska disclosed CVE-2026-66723 and CVE-2026-66724 on 2026-07-29 and stated both missing authorization vulnerabilities were fixed in MWDB Core version 2.19.0. The issues affected MWDB Core versions before 2.19.0, with one enabling abuse of the Remote Instances proxy API and the other bypassing capability checks on deprecated endpoints.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.