# CVE-2026-13082: GD::SecurityImage versions through 1.75 for Perl use rand to generate secrets

> Attackers can predict CAPTCHA challenges in GD::SecurityImage due to weak random number generation, bypassing bot protection mechanisms.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-13082, GHSA-p496-rgmp-v9mg, UBUNTU-CVE-2026-13082

## What is CVE-2026-13082?

CVE-2026-13082 is a medium-severity vulnerability in BURAK GD::SecurityImage, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GD::SecurityImage versions through 1.75 for Perl use rand to generate secrets.

The random method creates the challenge text used for the CAPTCHA by sampling characters from an array using Perl's built-in rand function, and generates a (by default) six-character string.

The built-in rand function is unsuitable for security applications because it is predictable and reversible.

Weakness: CWE-804 (Guessable CAPTCHA), CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2026-13082?


## How do I fix CVE-2026-13082?

No fix has been published for CVE-2026-13082 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-13082 being exploited?

There is no known exploitation of CVE-2026-13082 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-13082 and fix it if it is affected.

What it is: CVE-2026-13082 is a medium-severity vulnerability in BURAK GD::SecurityImage, published on 17 Jul 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 CVE-2026-13082 in the wild and no public exploit code.

Affected product: BURAK GD::SecurityImage. No package-level version data is available, so check the vendor advisory linked from the reference page.

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/CVE-2026-13082/ (Markdown: https://insights.sbomify.com/CVE-2026-13082/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-13082
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-13082
- OSV: https://osv.dev/vulnerability/CVE-2026-13082

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-13082/
Summaries are generated and may contain mistakes; the official description above is the record.