# GHSA-j443-wcqq-xprh: Terraform Provider for SendGrid: TLS Session Resumption Bypasses Certificate Authority Trust Store Modifications in Go

> Go TLS session resumption bypasses CA trust store updates, allowing revoked clients to reconnect if server config changes between connections.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2026
- **Also known as:** GO-2026-4673

## What is GHSA-j443-wcqq-xprh?

GHSA-j443-wcqq-xprh is a vulnerability in github.com/arslanbekov/terraform-provider-sendgrid, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

### Summary

A critical vulnerability has been identified at https://security.snyk.io/package/linux/chainguard:latest/terraform-provider-sendgrid, associated with the underlying Go version.

If the server's TLS configuration is mutated between connections — for example, a CA is removed from the trusted list via `Config.Clone()` combined with modification or `GetConfigForClient` — the resumed handshake still succeeds using the cached session. The certificate is not re-checked against the updated CA list.

As a result, a client whose CA was revoked or removed between the first and second connection could still establish a connection on the resumed session.

### Details

If the server's TLS configuration is mutated between connections — for example, a CA is removed from the trusted list via `Config.Clone()` combined with modification or `GetConfigForClient` — the resumed handshake still succeeds using the cached session. The certificate is not re-checked against the updated CA list.

Consequently, a client whose CA was revoked or removed between the first and second connection could still establish a connection on the resumed session.

## Which versions are affected by GHSA-j443-wcqq-xprh?

3 open source packages ship an affected version, including github.com/arslanbekov/terraform-provider-sendgrid.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/arslanbekov/terraform-provider-sendgrid` | Go | All versions | None |
| `github.com/arslanbekov/terraform-provider-sendgrid` | Go | All versions to 1.1.3-0.20250606002314-b4a2dfeb7b0f | None |
| `github.com/arslanbekov/terraform-provider-sendgrid` | Go | All versions to 1.1.3-0.20250606002314-b4a2dfeb7b0f | None |

## How do I fix GHSA-j443-wcqq-xprh?

No fix has been published for GHSA-j443-wcqq-xprh yet. Limit exposure of the affected software until one is available.

## Is GHSA-j443-wcqq-xprh being exploited?

There is no known exploitation of GHSA-j443-wcqq-xprh in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-j443-wcqq-xprh and fix it if it is affected.

What it is: GHSA-j443-wcqq-xprh is a vulnerability in github.com/arslanbekov/terraform-provider-sendgrid, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-j443-wcqq-xprh in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/arslanbekov/terraform-provider-sendgrid (Go): affected all versions; no fix listed
- github.com/arslanbekov/terraform-provider-sendgrid (Go): affected all versions up to 1.1.3-0.20250606002314-b4a2dfeb7b0f; no fix listed
- github.com/arslanbekov/terraform-provider-sendgrid (Go): affected all versions up to 1.1.3-0.20250606002314-b4a2dfeb7b0f; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-j443-wcqq-xprh/ (Markdown: https://insights.sbomify.com/GHSA-j443-wcqq-xprh/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-j443-wcqq-xprh

---
From sbomify Insights: https://insights.sbomify.com/GHSA-j443-wcqq-xprh/
Summaries are generated and may contain mistakes; the official description above is the record.