fixnx
highCVE-2026-45077

CVE-2026-45077 in Symfony Monolog Bridge

Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Prior to 5.4.52, 6.4.40, 7.4.12, and 8.0.12, the server:log listener (Symfony\Bridge\Monolog\Command\ServerLogCommand) binds to 0.0.0.0:9911 by default and...

ProductSymfony Monolog Bridge
CVSS8.3
EPSS0.00551
UpdatedJuly 15, 2026

Quick answer

Symfony Monolog Bridge should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • symfony/monolog-bridge <5.4.52
  • symfony/monolog-bridge >=6.0 <6.4.40
  • symfony/monolog-bridge >=7.0 <7.4.12
  • symfony/monolog-bridge >=8.0 <8.0.12

Fixed versions

  • symfony/monolog-bridge 5.4.52, 6.4.40, 7.4.12, or 8.0.12

How to fix it

Update Symfony Monolog Bridge. The old package can let a bad request slow the app, pass a login check, or run unsafe data.

  1. Update symfony/monolog-bridge to symfony/monolog-bridge 5.4.52, 6.4.40, 7.4.12, or 8.0.12 with Composer.
  2. Run the app tests.
  3. Clear Symfony cache and deploy.
  4. Check the app logs after release.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Run composer show symfony/monolog-bridge and confirm the fixed version is installed.
  • Scan again and confirm CVE-2026-45077 is gone.

Related categories

PHPWeb ApplicationRemote Code ExecutionUnsafe Deserialization

Trusted references

Source advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVDSource advisoryNVD

FAQ

What is affected by CVE-2026-45077?

Symfony Monolog Bridge versions listed as affected should be reviewed: symfony/monolog-bridge <5.4.52, symfony/monolog-bridge >=6.0 <6.4.40, symfony/monolog-bridge >=7.0 <7.4.12, symfony/monolog-bridge >=8.0 <8.0.12.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.