Account compromise via unrestricted login attempts
Published Sep 21, 2025 · Updated Sep 22, 2025
Improper restriction of authentication attempts in Harness 3.3.0 allows remote attackers to guess credentials via /api/v1/login. The login endpoint accepts repeated authentication attempts without sufficient frequency controls, exposing a credential-guessing oracle. No authentication is required to send attempts, but exploitation has high complexity and disclosure requires successful credential guessing.
Summary
What happened
Improper restriction of authentication attempts in Harness 3.3.0 allows remote attackers to guess credentials via /api/v1/login. The login endpoint accepts repeated authentication attempts without sufficient frequency controls, exposing a credential-guessing oracle. No authentication is required to send attempts, but exploitation has high complexity and disclosure requires successful credential guessing.
The record
- CVE
- CVE-2025-10761
- Published
- Sep 21, 2025
- Updated
- Sep 22, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-799, CWE-307, T1110.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 21, 2025CVE publishedPublication date reported by the CVE source.
- Sep 22, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo