CVE-2025-3261 ThingsBoard allows an authenticated user to upload malicious SVG images
Not scored
Published
Updated
Check this codebase for CVE-2025-3261 and fix it if it is affected.
What it is: CVE-2025-3261 is a vulnerability in org.thingsboard:application, published on 27 Nov 2025.
Exploitation: There is no known exploitation of CVE-2025-3261 in the wild and no public exploit code.
Affected packages and fixed versions:
- org.thingsboard:application (Maven): affected all versions; fixed in 4.2.1
- org.thingsboard:application (Maven): affected all versions; fixed in 4.2.1
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-2025-3261/ (Markdown: https://insights.sbomify.com/CVE-2025-3261/index.md)
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2025-3261?
CVE-2025-3261 is a vulnerability in org.thingsboard:application, published on 27 Nov 2025.
Official description
This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.
Which versions are affected by CVE-2025-3261?
2 open source packages ship an affected version, including org.thingsboard:application.
| Package | Affected | Fixed in |
|---|---|---|
org.thingsboard:application Maven | All versions | 4.2.1 |
org.thingsboard:application Maven | All versions | 4.2.1 |
How do I fix CVE-2025-3261?
Upgrade org.thingsboard:application to 4.2.1 or later.
Is CVE-2025-3261 being exploited?
There is no known exploitation of CVE-2025-3261 in the wild and no public exploit code.
Sources
Also known as GHSA-5p82-2q3r-wj3m.