CVE-2026-119049 FreeMail before 5.3.2 Authorization Bypass via /api/create Mailbox Claiming
High 7.2
Published
Updated
Check this codebase for CVE-2026-119049 and fix it if it is affected.
What it is: CVE-2026-119049 is a high-severity vulnerability in idinging FreeMail, published on 29 Oct 2026.
Exploitation: There is no known exploitation of CVE-2026-119049 in the wild and no public exploit code.
Affected product: idinging FreeMail. 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-119049/ (Markdown: https://insights.sbomify.com/CVE-2026-119049/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2026-119049?
CVE-2026-119049 is a high-severity vulnerability in idinging FreeMail, published on 29 Oct 2026.
Official description
FreeMail before 5.3.2 contains an authorization bypass vulnerability that allows authenticated users to claim another user's existing mailbox via the POST /api/create endpoint. Attackers who know a victim's address can become co-owners through assignMailboxToUser to read messages and verification codes, set forwarding, and delete mail.
Weakness: CWE-639
Which versions are affected by CVE-2026-119049?
How do I fix CVE-2026-119049?
No fix has been published for CVE-2026-119049 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-119049 being exploited?
There is no known exploitation of CVE-2026-119049 in the wild and no public exploit code.
Sources
Also known as GHSA-7mjv-78r5-wjqw.