# CVE-2026-118991: CallBackery versions before 0.62.0 for Perl encrypt configuration backups with the padded password as the AES key


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 30 Oct 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-8xrx-f9pw-qp4w

## What is CVE-2026-118991?

CVE-2026-118991 is a high-severity vulnerability in CallBackery, published on 30 Oct 2026. 

### Official description

CallBackery versions before 0.62.0 for Perl encrypt configuration backups with the padded password as the AES key.

getCrypt() pads the backup password with "x" characters and cuts it to 32 bytes to form the AES key, with no salt and no key derivation. The first block of a backup holds a 16 hex digit length field, so decrypting one block confirms a password guess at raw AES speed.

An attacker who obtains a backup can recover its password by fast offline guessing, and with it every credential the backup holds.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

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

1 open source package ship an affected version, including CallBackery.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `CallBackery` | cpan | `pkg:cpan/CallBackery` | All versions | 0.62.0 |

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

Upgrade CallBackery to 0.62.0 or later.

## Is CVE-2026-118991 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-118991 is a high-severity vulnerability in CallBackery, published on 30 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-118991 in the wild and no public exploit code.

Affected packages and fixed versions:
- CallBackery (cpan): affected all versions; fixed in 0.62.0

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

## Sources

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

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