CVE-2025-6517: A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical

Q: How do I fix CVE-2025-6517?

maxkey: upgrade to newer than 4.1.7. Exact commands for each OS are on this page.

Q: Is CVE-2025-6517 being exploited?

CVE-2025-6517 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2025-6517 affect?

CVE-2025-6517 affects maxkey. Severity is medium (CVSS 6.3). A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical. This issue affects the function Add of the file maxkey-webs\maxkey-web-mgt\src\main\java\org\dromara\maxkey\web\apps\contorller\SAML20DetailsController.java

Q: How urgent is CVE-2025-6517?

Priority 38/100. Public exploit reference

Routine

MEDIUM 6.3UPGRADE

CVE-2025-6517 is a medium-severity flaw (CVSS 6.3) affecting maxkey. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical. This issue affects the function Add of the file maxkey-webs\maxkey-web-mgt\src\main\java\org\dromara\maxkey\web\apps\contorller\SAML20DetailsController.java of the component Meta URL Handler. The manipulation of the argument post leads to server-side request forgery. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	6.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.5% (top 55%)
CISA exploited list	No
Weakness	CWE-918
Published	2025-06-23
Last modified	2026-06-17

Publisher (CNA): VulDB · Vendor: maxkey

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-06-23 18:15 UTCPublished CVE record published
2026-06-17 10:02 UTCUpdated Record last modified

maxkey maxkey UPGRADE

Affected: <= 4.1.7

Fixed in: newer than 4.1.7

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy maxkey || rpm -q maxkey || maxkey --version

2. UPGRADE to newer than 4.1.7 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade maxkey

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade maxkey

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-6517?

maxkey: upgrade to newer than 4.1.7. Exact commands for each OS are on this page.

Is CVE-2025-6517 being exploited?

CVE-2025-6517 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-6517 affect?

CVE-2025-6517 affects maxkey. Severity is medium (CVSS 6.3). A vulnerability was found in Dromara MaxKey up to 4.1.7 and classified as critical. This issue affects the function Add of the file maxkey-webs\maxkey-web-mgt\src\main\java\org\dromara\maxkey\web\apps\contorller\SAML20DetailsController.java

How urgent is CVE-2025-6517?

Priority 38/100. Public exploit reference

Software pages

Java vulnerabilities

References

← Back to latest CVEs