# CVE-2025-48382: Fess has Insecure Temporary File Permissions

> Local attackers can read sensitive data from insecure temporary files created by Fess in multi-user environments.

- **Severity:** Low 1.2 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 May 2025
- **Updated:** 27 May 2025
- **Also known as:** GHSA-g88v-2j67-9rmx

## What is CVE-2025-48382?

CVE-2025-48382 is a low-severity vulnerability in codelibs fess, published on 27 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Fess is a deployable Enterprise Search Server. Prior to version 14.19.2, the createTempFile() method in org.codelibs.fess.helper.SystemHelper creates temporary files without explicitly setting restrictive permissions. This could lead to potential information disclosure, allowing unauthorized local users to access sensitive data contained in these files. This issue primarily affects environments where Fess is deployed in a shared or multi-user context. Typical single-user or isolated deployments have minimal or negligible practical impact. This issue has been patched in version 14.19.2. A workaround for this issue involves ensuring local access to the environment running Fess is restricted to trusted users only.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2025-48382?

2 open source packages ship an affected version, including org.codelibs.fess:fess. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.codelibs.fess:fess` | Maven | All versions | 14.19.2 |
| `org.codelibs.fess:fess` | Maven | All versions | 14.19.2 |

Products: Codelibs Fess.

## How do I fix CVE-2025-48382?

Upgrade org.codelibs.fess:fess to 14.19.2 or later.

## Is CVE-2025-48382 being exploited?

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

## Other vulnerabilities in codelibs fess

- [CVE-2018-1000822](https://insights.sbomify.com/CVE-2018-1000822/): XML External Entity (XXE) vulnerability in codelibs fess (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-48382 and fix it if it is affected.

What it is: CVE-2025-48382 is a low-severity vulnerability in codelibs fess, published on 27 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-48382 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.codelibs.fess:fess (Maven): affected all versions; fixed in 14.19.2
- org.codelibs.fess:fess (Maven): affected all versions; fixed in 14.19.2

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-48382/ (Markdown: https://insights.sbomify.com/CVE-2025-48382/index.md)
```

## Sources

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

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