CVE-2025-65730
Pommee Goaway hard-coded credentials
- Published5 Dec 2025
Description
Authentication Bypass via Hardcoded Credentials GoAway up to v0.62.18, fixed in 0.62.19, uses a hardcoded secret for signing JWT tokens used for authentication.
CVSS 3.1 breakdown
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://github.com/gian2dchris/CVEs/tree/CVE-2025-65730/CVE-2025-65730
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/auth.go#L48
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/middleware.go#L110
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/middleware.go#L15
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/middleware.go#L40
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/middleware.go#L69
- https://github.com/pommee/goaway/blob/v0.62.18/backend/api/middleware.go#L88
- https://github.com/pommee/goaway/commit/5769f8782b7453ca1c22a201b224b5ce48532f64#diff-4ddfd6cf1311ddfd45734bb1dc53bc208df69584ba92ac4f38866bd558434678L15-L40
- https://github.com/pommee/goaway/releases/tag/v0.62.16
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-65730 being actively exploited?
CVE-2025-65730 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 0.52%.
How severe is CVE-2025-65730?
CVE-2025-65730 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.52% probability of exploitation.
Which products are affected by CVE-2025-65730?
Affected products include Pommee Goaway.
How do I fix CVE-2025-65730?
Upgrade affected software to a fixed version, for example Pommee Goaway 0.62.19 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-65730 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.