CVE-2025-10760: Harness · Server-Side Request Forgery
Affects HarnessSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:PExploitation evidence
Disclosed: evidence found.
CVE published 21 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Harness | Affected
| Fixed in– |
AI-suggested
Immediate mitigation steps include restricting network access to Harness instances, ensuring they are not publicly accessible unless absolutely necessary. Implement strict egress filtering on the network to limit outbound requests from the Harness server to only trusted destinations, preventing SSRF from reaching internal or cloud metadata services. Employ web application firewalls (WAFs) with rules tuned to detect and block SSRF patterns targeting the 'url' parameter in the LookupRepo function. Monitor logs for unusual outbound requests originating from Harness servers. If possible, disable or restrict the LookupRepo functionality until a vendor patch is available. Conduct internal code reviews or penetration tests to identify other potential SSRF vectors. Organizations should also consider deploying runtime application self-protection (RASP) solutions to detect and block SSRF attempts in real time. Finally, maintain an inventory of all Harness instances and upgrade to patched versions promptly once available, or apply vendor-provided workarounds if released.
Description
A flaw has been found in Harness 3.3.0. This impacts the function LookupRepo of the file app/api/controller/gitspace/lookup_repo.go. Executing manipulation of the argument url can lead to server-side request forgery. The attack may be launched remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.