Skip to content

Pekko Management may not properly apply authenticator when Basic Authentication is enabled

Moderate severity GitHub Reviewed Published Jun 3, 2025 to the GitHub Advisory Database • Updated Nov 14, 2025

Package

maven com.lightbend.akka.management:akka-management_2.12 (Maven)

Affected versions

< 1.6.1

Patched versions

1.6.1
maven com.lightbend.akka.management:akka-management_2.13 (Maven)
< 1.6.1
1.6.1
maven com.lightbend.akka.management:akka-management_3 (Maven)
< 1.6.1
1.6.1
maven org.apache.pekko:pekko-management_2.12 (Maven)
< 1.1.1
1.1.1
maven org.apache.pekko:pekko-management_2.13 (Maven)
< 1.1.1
1.1.1
maven org.apache.pekko:pekko-management_3 (Maven)
< 1.1.1
1.1.1

Description

If you enable Basic Authentication in Pekko Management using the Java DSL, the authenticator may not be properly applied.

Users that rely on authentication instead of making sure the Management API ports are only available to trusted users are recommended to upgrade to version 1.1.1, which fixes this issue. Akka was affected by the same issue and has released the fix in version 1.6.1.

References

Published by the National Vulnerability Database Jun 3, 2025
Published to the GitHub Advisory Database Jun 3, 2025
Reviewed Jun 6, 2025
Last updated Nov 14, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(70th percentile)

Weaknesses

Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct. Learn more on MITRE.

CVE ID

CVE-2025-46548

GHSA ID

GHSA-9qvj-rpj8-v5c8

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.