high · 7.1 Partly patched

CTFer.io's CTFd Terraform Provider allows a local or remote attacker to read team passwords in state as non sensitive values

CVE-2026-116683 · GHSA-vg84-c5mg-76xh · published 27 Oct 2026

How serious is it

  • Severity: high, CVSS score 7.1 out of 10.
  • No exploit prediction (EPSS) score yet.
  • Not on the CISA list of exploited vulnerabilities.
  • No public exploit in Exploit-DB.

Is your app affected by CVE-2026-116683?

Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.

Who is affected

  • github.com/ctfer-io/terraform-provider-ctfd (Go) >= 0.1.5, <= 1.1.0
  • github.com/ctfer-io/terraform-provider-ctfd/v2 (Go) < 2.8.2

How to check

  1. Run go list -m github.com/ctfer-io/terraform-provider-ctfd in your project to see the installed version, including copies pulled in by other packages.
  2. Run go list -m github.com/ctfer-io/terraform-provider-ctfd/v2 in your project to see the installed version, including copies pulled in by other packages.
  3. Or paste your lockfile into the checker: it lists every package with a known vulnerability, this one included.

How to fix

Copies a prompt for Claude Code, Cursor or Codex: it checks your lockfiles for this and upgrades it.
  1. No fixed version of github.com/ctfer-io/terraform-provider-ctfd yet. Replace or remove it, or apply the workaround in the advisory below.
  2. On < 2.8.2: Upgrade github.com/ctfer-io/terraform-provider-ctfd/v2 to 2.8.2 or later, commit the lockfile and redeploy.
  3. If a vulnerable version was live, check your logs and rotate the secrets that server could read.

The advisory

### Impact CTFer.io's CTFd Terraform Provider stores `ctfd_team.password` as non-sensitive values (CWE-522). A local or remote attacker, who can have access to the Terraform state, can read team passwords without the need for the state password for decryption. ### Patches Patched in v2.8.2. ### Workarounds No workaround exist, yet CTFer.io recommends you keep your state in safe environments with a limited set of users who can access it as a good practice to avoid exploitation of this vulnerability.

Check your whole app

Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.

References

Merged from GitHub Advisory Database, OSV. Last updated 28 Oct 2026. All vulnerabilities · RSS · JSON

Get alerts for new exploited vulnerabilities