# CVE-2026-82604: BareBones BBEdit Java Language recursion


- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 31 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** GHSA-8466-79gg-53v6

## What is CVE-2026-82604?

CVE-2026-82604 is a medium-severity vulnerability in BareBones BBEdit, published on 31 Aug 2026. 

### Official description

A flaw has been found in BareBones BBEdit up to 15.5.5. Impacted is an unknown function of the component Java Language Module. This manipulation causes uncontrolled recursion. Remote exploitation of the attack is possible. Upgrading to version 16.0 is recommended to address this issue. You should upgrade the affected component.

Weakness: CWE-674 (Uncontrolled Recursion), CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2026-82604 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-82604 is a medium-severity vulnerability in BareBones BBEdit, published on 31 Aug 2026. 
Exploitation: There is no known exploitation of CVE-2026-82604 in the wild and no public exploit code.

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

## Sources

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

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