# CVE-2026-48780: Forem vulnerable to bypass of email address domain restrictions

> Attackers can bypass email domain restrictions to gain unauthorized access to invite-only Forem community deployments.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 16 Jun 2026
- **Updated:** 17 Jun 2026
- **Also known as:** GHSA-3g4h-9h37-mpx6

## What is CVE-2026-48780?

CVE-2026-48780 is a high-severity authentication bypass vulnerability in forem, published on 16 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Forem is open source software for building communities. Prior to commit a2ab6d4, a maliciously crafted email address could allow an attacker to bypass domain allowlist or denylist restrictions and gain access to invite-only forem deployments. The issue is patched as of `a2ab6d4`. As a workaround, some SMTP servers and email delivery providers may drop or refuse to send maliciously crafted email addresses.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-48780 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-48780 is a high-severity authentication bypass vulnerability in forem, published on 16 Jun 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-48780 in the wild and no public exploit code.

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

## Sources

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

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