# CVE-2026-16643: Lunr exposed filters - Critical - Unsupported - SA-CONTRIB-2026-086

> Critical vulnerability in the unsupported Drupal Lunr exposed filters module requires immediate attention due to lack of support.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Aug 2026
- **Updated:** 26 Aug 2026
- **Also known as:** DRUPAL-CONTRIB-2026-086, GHSA-r289-9gv7-8c69

## What is CVE-2026-16643?

CVE-2026-16643 is a medium-severity vulnerability in Drupal Lunr exposed filters, published on 25 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Vulnerability in Drupal Lunr exposed filters. This issue affects Lunr exposed filters versions: *.*.

Weakness: CWE-20 (Improper Input Validation)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `drupal/lunr_filters` | Packagist:https://packages.drupal.org/8 | All versions | None |

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

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

## Is CVE-2026-16643 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-16643 is a medium-severity vulnerability in Drupal Lunr exposed filters, published on 25 Aug 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-16643 in the wild and no public exploit code.

Affected product: Drupal Lunr exposed filters. 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-16643/ (Markdown: https://insights.sbomify.com/CVE-2026-16643/index.md)
```

## Sources

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

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