Skip to main content
VulnerabilityPublished

CVE-2026-66723: CERT.PL MWDB Core · Missing Authorization

Affects CERT.PL MWDB CoreSource CVE Database V5

0

Not known to be exploited · CVSS 7.0 High : upgrade to 2.19.0 soon.

Data as of 27 Oct 2026, 17:11 UTC

CVSS 4.0 base score
7.0High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.19.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade MWDB Core and mwdb-core to 2.19.0.

Affected software

ProductAffectedFixed in
CERT.PLMWDB CoreAffected
  • >=2.2.0 <2.19.0
Fixed in
  • 2.19.0
GitHubmwdb-corepkg:github/mwdb-coreOther threatsAffected
  • >=2.2.0 <2.19.0
Fixed in
  • 2.19.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade MWDB Core to version 2.19.0 or later, where this vulnerability has been fixed. There is no indication of an official temporary fix or workaround, so applying the official patch is the recommended remediation.

Description

MWDB Core versions >=2.2.0 and <2.19.0 contain a missing authorization vulnerability in the Remote Instances proxy API. The proxy API does not verify authentication for incoming requests, allowing an unauthenticated remote attacker to send arbitrary requests to a remote MWDB instance using the identity and permissions associated with the configured API key. This can result in unauthorized actions being performed on the remote instance as if executed by the user whose API key was used to set up the remote instance. The vulnerability is limited to deployments where Remote Instances have been configured.This issue has been fixed in version 2.19.0

References

Community reviews

Loading reviews…