CVE-2026-35037: Server-Side Request Forgery in Go
// Executive Summary
The GET /api/website/title endpoint accepts an arbitrary URL via the website_url query parameter and makes a server-side HTTP request to it without any validation of the target host or IP address. The endpoint requires no authentication. An attacker can use this to reach internal network services, cloud metadata endpoints (169.254.169.254), and localhost-bound services, with partial response data exfiltrated via the HTML <title> tag extraction.
The CVE-2026-35037 vulnerability affects Go and represents a high-severity Server-Side Request Forgery flaw with real-world consequences for organizations running affected versions.
Internal Network Reconnaissance
Attackers can probe internal services, cloud metadata endpoints, and localhost-bound applications.
Cloud Credential Theft
AWS/GCP/Azure instance metadata endpoints can be queried to steal IAM credentials and API tokens.
Firewall Bypass
The vulnerable server acts as a proxy, bypassing network ACLs to reach otherwise-protected infrastructure.
Follow these steps to determine whether your systems are exposed to CVE-2026-35037:
Detection Checklist
- Identify all instances of Go deployed in your environment (on-premises, cloud, and containerized deployments).
- Check the version of your Go installation — vulnerable versions are indicated in the CVE advisory.
- Review access logs for anomalous request patterns consistent with Server-Side Request Forgery exploitation attempts.
- Search for indicators of compromise (IOCs) including unexpected process spawns, unusual network connections, or modified configuration files.
- Run KENSAI's automated vulnerability scanner against your Go deployment to confirm exposure in minutes.
- Check your SIEM/IDS for alerts referencing this CVE or related attack signatures published by threat intelligence vendors.
Immediate Actions Required
- Apply the vendor patch immediately — update Go to the latest patched version as specified in the CVE advisory.
- If an immediate patch is not possible, implement temporary mitigations such as WAF rules to block exploit attempts.
- Isolate the affected system from the internal network until patched to prevent lateral movement by attackers.
- Enforce multi-factor authentication (MFA) on all accounts with access to the affected system as an additional defense-in-depth measure.
- Restrict network access to the vulnerable component using firewall rules, limiting exposure to trusted IP ranges only.
- Audit and rotate all credentials (passwords, API keys, tokens) that may have been accessible to an attacker if exploitation occurred.
- Enable comprehensive logging and alerting for the affected component to detect any ongoing exploitation attempts.
- Conduct a post-patch verification scan to confirm the vulnerability has been remediated before returning the system to production.
- Review related systems and dependencies that may be affected by the same vulnerability class.
What is CVE-2026-35037?
CVE-2026-35037 is a high-severity Server-Side Request Forgery vulnerability affecting Go. It has a CVSS score of 7.2 and requires immediate attention from security teams.
How serious is CVE-2026-35037?
With a HIGH severity rating and CVSS score of 7.2, CVE-2026-35037 represents a significant security risk. Organizations using Go should treat remediation as a high priority.
Is CVE-2026-35037 actively exploited?
Security researchers have published details about this vulnerability. Monitor CISA's KEV catalog and your threat intelligence feeds for exploitation status updates. Apply the patch regardless of current exploitation status.
How do I fix CVE-2026-35037?
The primary remediation is to apply the vendor-supplied patch for Go. If patching is not immediately possible, implement temporary compensating controls such as WAF rules or network access restrictions while the patch is scheduled.
Does CVE-2026-35037 affect my organization?
If your organization uses Go, you should assess your exposure immediately. Check the specific affected versions in the CVE advisory and run an automated vulnerability scan to confirm your exposure status.