CVE-2025-15105: A security flaw has been discovered in getmaxun maxun up to 0.0.28

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

maxun: upgrade to newer than 0.0.28. Exact commands for each OS are on this page.

Q: Is CVE-2025-15105 being exploited?

CVE-2025-15105 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-15105 affect?

CVE-2025-15105 affects maxun. Severity is low (CVSS 3.7). A security flaw has been discovered in getmaxun maxun up to 0.0.28. Impacted is an unknown function of the file /getmaxun/maxun/blob/develop/server/src/routes/auth.ts. Performing manipulation of the argument api_key results in use of hard-c

Q: How urgent is CVE-2025-15105?

Priority 34/100. Public exploit reference; Remotely exploitable, no login, no user action

This week

LOW 3.7REMOTEUPGRADE

CVE-2025-15105 is a low-severity flaw (CVSS 3.7) affecting maxun. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A security flaw has been discovered in getmaxun maxun up to 0.0.28. Impacted is an unknown function of the file /getmaxun/maxun/blob/develop/server/src/routes/auth.ts. Performing manipulation of the argument api_key results in use of hard-coded cryptographic key . Remote exploitation of the attack is possible. The attack is considered to have high complexity. The exploitability is considered difficult. The exploit has been released to the public

Why this priority

Public exploit reference
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	3.7 (Low)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	0.5% (top 56%)
CISA exploited list	No
Weakness	CWE-320, CWE-321, CWE-798
Published	2025-12-27
Last modified	2026-10-07

Publisher (CNA): VulDB · Vendor: maxun

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

Am I affected?

Timeline

2025-12-27 09:15 UTCPublished CVE record published
2026-10-07 13:10 UTCUpdated Record last modified

maxun maxun UPGRADE

Affected: <= 0.0.28

Fixed in: newer than 0.0.28

Safe to downgrade to: no unaffected older release

1. Check installed version

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

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

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

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade maxun

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-15105?

maxun: upgrade to newer than 0.0.28. Exact commands for each OS are on this page.

Is CVE-2025-15105 being exploited?

CVE-2025-15105 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-15105 affect?

CVE-2025-15105 affects maxun. Severity is low (CVSS 3.7). A security flaw has been discovered in getmaxun maxun up to 0.0.28. Impacted is an unknown function of the file /getmaxun/maxun/blob/develop/server/src/routes/auth.ts. Performing manipulation of the argument api_key results in use of hard-c

How urgent is CVE-2025-15105?

Priority 34/100. Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2025-15106 MEDIUM 6.3 UPGRADE A weakness has been identified in getmaxun maxun up to 0.0.28

References

← Back to latest CVEs