Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Ibexa Kernel's files with blacklisted extensions can be still saved to drafts

GHSA-9j39-4686-m3c4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (ibexa/core 4.6.2, 4.5.6), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist ibexa/core

    Affected
    >= 4.5.0, < 4.5.6>= 4.6.0, < 4.6.2
    Fixed in
    4.6.2, 4.5.6

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

Impact File validation can be configured to reject certain files by file type. When this happens, validation fails, and the content can't be published. However, the file can be saved when saving the content draft. This means unwanted files can be present in storage, even if they are not easily accessible due to the content not being published. The fix ensures these unwanted file types are never stored. An attacker would need to have existing access to create content with a file field type to exploit this. Patches See "Patched versions". Commit: https://github.com/ibexa/core/commit/7e472317f7c75f45f72f74c38406952d8bea0de1 References https://developers.ibexa.co/security-advisories/ibexa-sa-2024-002-file-validation-and-workflow-stages

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-9j39-4686-m3c4

Agent brief

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

# Patch Next advisory brief: GHSA-9j39-4686-m3c4

Advisory: Ibexa Kernel's files with blacklisted extensions can be still saved to drafts
IDs: GHSA-9j39-4686-m3c4
Record: https://patchnext.com/advisories/ghsa-9j39-4686-m3c4 (revision 1, source checked 26 Oct 2026, 14:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: ibexa/core 4.6.2, 4.5.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist ibexa/core: affected >= 4.5.0, < 4.5.6; >= 4.6.0, < 4.6.2; fixed in 4.6.2, 4.5.6

## Suggested inspection (read-only)
- Packagist ibexa/core: 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 ibexa/core.
- 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-9j39-4686-m3c4 (GitHub-reviewed advisory GHSA-9j39-4686-m3c4 lists affected ranges: Packagist ibexa/core >=4.5.0 =4.6.0 <4.6.2)

Commands are suggestions: review each one before running it.

Loading voting…