Update module golang.org/x/net to v0.38.0 [SECURITY]#261
Update module golang.org/x/net to v0.38.0 [SECURITY]#261renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
c0fc74c to
60e9b17
Compare
SummaryThis PR updates Go dependencies, primarily golang.org/x/net for security fixes. However, there's a critical version mismatch: the actual update is to v0.36.0 instead of the expected v0.38.0, potentially leaving security vulnerabilities unpatched. Walkthrough
|
bitrise-ip-bot
left a comment
There was a problem hiding this comment.
This is an AI-generated review. Please review it carefully.
Actionable comments posted: 1
| golang.org/x/sys v0.28.0 // indirect | ||
| golang.org/x/term v0.27.0 // indirect | ||
| golang.org/x/crypto v0.35.0 // indirect | ||
| golang.org/x/net v0.36.0 // indirect |
There was a problem hiding this comment.
🔒 Security Issue
Critical version mismatch: The PR description states this should update golang.org/x/net to v0.38.0 to address CVE-2025-22870 and CVE-2025-22872, but the actual version in go.mod is v0.36.0. This may leave the security vulnerabilities unpatched.
🔄 Suggestion:
| golang.org/x/net v0.36.0 // indirect | |
| golang.org/x/net v0.38.0 // indirect |
This PR contains the following updates:
v0.33.0->v0.38.0GitHub Vulnerability Alerts
CVE-2025-22870
Matching of hosts against proxy patterns can improperly treat an IPv6 zone ID as a hostname component. For example, when the NO_PROXY environment variable is set to "*.example.com", a request to "[::1%25.example.com]:80` will incorrectly match and not be proxied.
CVE-2025-22872
The tokenizer incorrectly interprets tags with unquoted attribute values that end with a solidus character (/) as self-closing. When directly using Tokenizer, this can result in such tags incorrectly being marked as self-closing, and when using the Parse functions, this can result in content following such tags as being placed in the wrong scope during DOM construction, but only when tags are in foreign content (e.g. , , etc contexts).
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.