# CVE-2026-123660: Vulnerability-Lookup: memory amplification through webhook payload template format specifiers


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 6 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-fjqr-7p2w-j9wx

## What is CVE-2026-123660?

CVE-2026-123660 is a medium-severity vulnerability in vulnerability-lookup, published on 6 Nov 2026. 

### Official description

In Vulnerability-Lookup 5.5.1 up to but not including 6.4.1, a signed-in user could make the server allocate memory far out of proportion to their input through a webhook notification's payload template. Each placeholder's format specifier was passed unchanged to Python's string formatting, which builds the padded result before its size can be checked. A template of a few dozen bytes, such as {"text": "{title:>999999999}"}, therefore produced a string of about 1 GB when the notification form test-rendered it on save, and repeating such fields multiplied the cost. Templates that passed the save check could also repeat placeholders such as {text} thousands of times; the notification daemon rebuilt those on every webhook delivery. Deeply nested templates raised an unhandled recursion error (HTTP 500). An attacker needs only an account, which the default configuration lets anyone create after e-mail confirmation. They could exhaust the memory of web workers or the notification daemon, causing a denial of service. Version 6.4.1 caps every number in a format specifier at 256, limits a rendered template to 1,000,000 characters both on save and at delivery, and rejects templates nested deeper than 32 levels.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-674 (Uncontrolled Recursion), CWE-1284 (Improper Validation of Specified Quantity in Input)

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


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

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

## Is CVE-2026-123660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-123660 is a medium-severity vulnerability in vulnerability-lookup, published on 6 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123660 in the wild and no public exploit code.

Affected product: vulnerability-lookup. 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-123660/ (Markdown: https://insights.sbomify.com/CVE-2026-123660/index.md)
```

## Sources

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

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