Skip to main content
CVE-2025-48382VulnerabilityPublished

CVE-2025-48382: codelibs fess · Incorrect Permissions

Affects codelibs fessSource CVE Database V5

0

Not known to be exploited · CVSS 1.2 Low : upgrade to 14.19.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
1.2Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 14.19.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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 May 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Upgrade codelibs/fess to 14.19.2.

Affected software

ProductAffectedFixed in
GitHubcodelibs/fesspkg:github/codelibs/fessOther threatsAffected
  • <14.19.2
Fixed in
  • 14.19.2

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Upgrade to Fess version 14.19.2 or later, where the vulnerability has been patched by enforcing restrictive permissions on temporary files. 2. Restrict local system access to trusted users only, especially on servers running Fess in multi-user environments. Implement strict user account management and monitoring to prevent unauthorized local access. 3. Employ operating system-level access controls such as mandatory access control (e.g., SELinux, AppArmor) or filesystem ACLs to further restrict access to Fess temporary directories. 4. Regularly audit file permissions and temporary file creation behavior on servers hosting Fess to detect any deviations from secure configurations. 5. Consider isolating Fess deployments in containerized or virtualized environments with limited local user access to minimize exposure. 6. Monitor logs for unusual local access patterns or attempts to access temporary files. 7. Educate system administrators and security teams about the importance of secure file permission management in enterprise applications.

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.

References

Community reviews

Loading reviews…