How severe is CVE-2025-48382?

No CVSS score has been assigned to CVE-2025-48382 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2025-48382?

CVE-2025-48382 affects the following packages: org.codelibs.fess:fess (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-48382?

Update org.codelibs.fess:fess to 14.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48382 is resolved across your whole dependency graph.

How do I detect CVE-2025-48382 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codelibs.fess:fess, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-48382 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2025-48382 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-48382 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-48382?

CVE-2025-48382 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 4th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-48382?

CVE-2025-48382 is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-48382 published, and has it been updated?

CVE-2025-48382 was published on May 27, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2025-48382 — fess

Fix: codelibs/fess@25b2009

CVE-2025-48382 is a CWE-732 vulnerability in org.codelibs.fess:fess. A fix is available for org.codelibs.fess:fess — see the affected versions and patch details below.

Fess has Insecure Temporary File Permissions

Also known asGHSA-g88v-2j67-9rmx

Published

May 27, 2025

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-48382.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs4th percentile — riskier than 4% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕org.codelibs.fess:fess

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

Fess (an open-source Enterprise Search Server) creates temporary files without restrictive permissions, which may allow local attackers to read sensitive information from these temporary files.

Details

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.

Impact

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.

Workarounds

Ensure local access to the environment running Fess is restricted to trusted users only.

References

CVE-2022-24823: Netty temporary file permissions vulnerability

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.codelibs.fess:fess`	all versions	14.19.2`org.codelibs.fess:fess:14.19.2`

Affected Products

1 product · 1 configurations

Application

fesscodelibs

< 14.19.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.codelibs.fess:fess, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.codelibs.fess:fess to 14.19.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-48382 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

### Summary Fess (an open-source Enterprise Search Server) creates temporary files without restrictive permissions, which may allow local attackers to read sensitive information from these temporary files. ### Details 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. ### Impact This issue primarily affects environments where Fess is deployed in a shared or mu

O3 Security · Impact-Aware SCA

Is CVE-2025-48382 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works