Fess has Insecure Temporary File Permissions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2025-48382: 0.15% estimated exploitation activity in the next 30 days; percentile 4.30 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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

Published by the source

27 May 2025, 18:00 UTC

Last modified by the source

28 May 2025, 14:29 UTC

Source last checked

26 Oct 2026, 16:36 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-g88v-2j67-9rmx

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2025-48382

Advisory: Fess has Insecure Temporary File Permissions
IDs: CVE-2025-48382, GHSA-g88v-2j67-9rmx
Record: https://patchnext.com/advisories/cve-2025-48382 (revision 1, source checked 26 Oct 2026, 16:36 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 1.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.codelibs.fess:fess 14.19.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.codelibs.fess:fess: affected < 14.19.2; fixed in 14.19.2

## Suggested inspection (read-only)
- Maven org.codelibs.fess:fess: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.codelibs.fess:fess.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-g88v-2j67-9rmx (GitHub-reviewed advisory GHSA-g88v-2j67-9rmx lists affected ranges: Maven org.codelibs.fess:fess >=0 <14.19.2)

Commands are suggestions: review each one before running it.