Vulnerable Library - symfony/monolog-bundle-v4.0.1
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Vulnerabilities
| Vulnerability |
Severity |
 CVSS |
Dependency |
Type |
Fixed in (symfony/monolog-bundle-v4.0.1 version) |
Remediation Possible** |
| CVE-2026-45077 |
 Critical |
9.8 |
symfony/monolog-bridge-v8.0.0 |
Transitive |
N/A* |
❌ |
| CVE-2026-45075 |
 High |
8.1 |
symfony/http-kernel-v8.0.2 |
Transitive |
N/A* |
❌ |
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
CVE-2026-45077
Vulnerable Library - symfony/monolog-bridge-v8.0.0
Provides integration for Monolog with various Symfony components
Library home page: https://api.github.com/repos/symfony/monolog-bridge/zipball/6dd0793eb9ebcecb0b909a5571ac6e82867d7b20
Dependency Hierarchy:
- symfony/monolog-bundle-v4.0.1 (Root Library)
- ❌ symfony/monolog-bridge-v8.0.0 (Vulnerable Library)
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Found in base branch: develop
Vulnerability Details
Description "Symfony\Bridge\Monolog\Command\ServerLogCommand" (the "server:log" console command) is a development-time helper that opens a TCP listener and displays log records pushed to it by the application's logging pipeline. Two unsafe defaults combine into a remotely reachable PHP object-deserialization sink: 1. The listener binds to "0.0.0.0:9911" by default; it accepts connections on every interface, not only loopback. 2. Each received frame is processed as "unserialize(base64_decode($message))" without an "allowed_classes" allowlist, without authentication, and without any integrity check. The decoded value is then passed to "displayLog(..., array $record)" which assumes (without validating) that the result is an array. Any host that can reach TCP port 9911 on a machine running "server:log" can therefore submit attacker-chosen serialized PHP payloads. The minimum impact is an unauthenticated denial of service (sending a non-array, e.g. "serialize(new stdClass())", crashes the listener with a type error). Object injection with magic-method side effects ("__wakeup()" / "__destruct()" / etc.) is reachable before the array type-check fires; full remote code execution is environment-dependent and contingent on usable gadget chains in the autoload set of the target process. Resolution The "server:log" command no longer binds to all interfaces by default: the default "--host" is now "127.0.0.1:9911", requiring explicit opt-in to accept off-host traffic. Message decoding is gated by an "unserialize()" allowlist restricted to the "Symfony\Component\VarDumper\Caster*" and "Symfony\Component\VarDumper\Cloner*" classes that legitimately appear inside dumped log records; any other class is rejected and the record discarded. The patch for this issue is available "here" (symfony/symfony@0891b2f) for branch 5.4. Credits Symfony would like to thank Toàn Thắng and Sam Sanoop for reporting the issue and Nicolas Grekas for fixing it.
Publish Date: 2026-05-31
URL: CVE-2026-45077
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2026-05-27
Fix Resolution: https://github.com/symfony/symfony.git - v5.4.52,https://github.com/symfony/symfony.git - v8.0.11,https://github.com/symfony/symfony.git - v7.4.11,https://github.com/symfony/symfony.git - v6.4.39
Step up your Open Source Security Game with Mend here
CVE-2026-45075
Vulnerable Library - symfony/http-kernel-v8.0.2
Provides a structured process for converting a Request into a Response
Library home page: https://api.github.com/repos/symfony/http-kernel/zipball/bcef77a3c8ae8934ce7067172e2a1a6491a62a7d
Dependency Hierarchy:
- symfony/monolog-bundle-v4.0.1 (Root Library)
- ❌ symfony/http-kernel-v8.0.2 (Vulnerable Library)
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Found in base branch: develop
Vulnerability Details
Description Symfony's "#[IsGranted('...')]", "#[IsSignatureValid]", and "#[IsCsrfTokenValid(...)]" attributes allow you to define a "methods: [...]" argument to only enforce these checks for the listed HTTP methods and skip them otherwise. E.g. an attribute defining "methods: ['GET']" would be ignored for a "HEAD" request. On the other hand, Symfony's router (and HTTP semantics generally) serves "HEAD" requests using the "GET" handler. Therefore, a controller protected by e.g. "#[IsGranted('ROLE_ADMIN', methods: ['GET'])]" can be reached via "HEAD" with the authorization check silently skipped. Even if the "HEAD" request won't get any response content, response headers leak ("Content-Length", "Location", custom headers). Also, the controller still executes and any side effects (DB writes, state changes) occur. Resolution When adding "GET" in the "methods" option of these attributes, Symfony now also include the "HEAD" method automatically. The patch for this issue is available "here" (symfony/symfony@fa8d5c6) for branch 7.4. Credits Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and Alexandre Daubois for fixing it.
Publish Date: 2026-05-31
URL: CVE-2026-45075
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.
Suggested Fix
Type: Upgrade version
Release Date: 2026-05-27
Fix Resolution: https://github.com/symfony/symfony.git - v5.4.52,https://github.com/symfony/symfony.git - v8.0.11,https://github.com/symfony/symfony.git - v7.4.11,https://github.com/symfony/symfony.git - v6.4.39
Step up your Open Source Security Game with Mend here
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Vulnerabilities
*For some transitive vulnerabilities, there is no version of direct dependency with a fix. Check the "Details" section below to see if there is a version of transitive dependency where vulnerability is fixed.
**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation
Details
Vulnerable Library - symfony/monolog-bridge-v8.0.0
Provides integration for Monolog with various Symfony components
Library home page: https://api.github.com/repos/symfony/monolog-bridge/zipball/6dd0793eb9ebcecb0b909a5571ac6e82867d7b20
Dependency Hierarchy:
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Found in base branch: develop
Vulnerability Details
Description "Symfony\Bridge\Monolog\Command\ServerLogCommand" (the "server:log" console command) is a development-time helper that opens a TCP listener and displays log records pushed to it by the application's logging pipeline. Two unsafe defaults combine into a remotely reachable PHP object-deserialization sink: 1. The listener binds to "0.0.0.0:9911" by default; it accepts connections on every interface, not only loopback. 2. Each received frame is processed as "unserialize(base64_decode($message))" without an "allowed_classes" allowlist, without authentication, and without any integrity check. The decoded value is then passed to "displayLog(..., array $record)" which assumes (without validating) that the result is an array. Any host that can reach TCP port 9911 on a machine running "server:log" can therefore submit attacker-chosen serialized PHP payloads. The minimum impact is an unauthenticated denial of service (sending a non-array, e.g. "serialize(new stdClass())", crashes the listener with a type error). Object injection with magic-method side effects ("__wakeup()" / "__destruct()" / etc.) is reachable before the array type-check fires; full remote code execution is environment-dependent and contingent on usable gadget chains in the autoload set of the target process. Resolution The "server:log" command no longer binds to all interfaces by default: the default "--host" is now "127.0.0.1:9911", requiring explicit opt-in to accept off-host traffic. Message decoding is gated by an "unserialize()" allowlist restricted to the "Symfony\Component\VarDumper\Caster*" and "Symfony\Component\VarDumper\Cloner*" classes that legitimately appear inside dumped log records; any other class is rejected and the record discarded. The patch for this issue is available "here" (symfony/symfony@0891b2f) for branch 5.4. Credits Symfony would like to thank Toàn Thắng and Sam Sanoop for reporting the issue and Nicolas Grekas for fixing it.
Publish Date: 2026-05-31
URL: CVE-2026-45077
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2026-05-27
Fix Resolution: https://github.com/symfony/symfony.git - v5.4.52,https://github.com/symfony/symfony.git - v8.0.11,https://github.com/symfony/symfony.git - v7.4.11,https://github.com/symfony/symfony.git - v6.4.39
Step up your Open Source Security Game with Mend here
Vulnerable Library - symfony/http-kernel-v8.0.2
Provides a structured process for converting a Request into a Response
Library home page: https://api.github.com/repos/symfony/http-kernel/zipball/bcef77a3c8ae8934ce7067172e2a1a6491a62a7d
Dependency Hierarchy:
Found in HEAD commit: 45fd85ad85cccc095b1d85471b9b73160b3006a7
Found in base branch: develop
Vulnerability Details
Description Symfony's "#[IsGranted('...')]", "#[IsSignatureValid]", and "#[IsCsrfTokenValid(...)]" attributes allow you to define a "methods: [...]" argument to only enforce these checks for the listed HTTP methods and skip them otherwise. E.g. an attribute defining "methods: ['GET']" would be ignored for a "HEAD" request. On the other hand, Symfony's router (and HTTP semantics generally) serves "HEAD" requests using the "GET" handler. Therefore, a controller protected by e.g. "#[IsGranted('ROLE_ADMIN', methods: ['GET'])]" can be reached via "HEAD" with the authorization check silently skipped. Even if the "HEAD" request won't get any response content, response headers leak ("Content-Length", "Location", custom headers). Also, the controller still executes and any side effects (DB writes, state changes) occur. Resolution When adding "GET" in the "methods" option of these attributes, Symfony now also include the "HEAD" method automatically. The patch for this issue is available "here" (symfony/symfony@fa8d5c6) for branch 7.4. Credits Symfony would like to thank Claude Mythos Preview (via Project Glasswing) for reporting the issue and Alexandre Daubois for fixing it.
Publish Date: 2026-05-31
URL: CVE-2026-45075
CVSS 3 Score Details (8.1)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: None
For more information on CVSS3 Scores, click here.Suggested Fix
Type: Upgrade version
Release Date: 2026-05-27
Fix Resolution: https://github.com/symfony/symfony.git - v5.4.52,https://github.com/symfony/symfony.git - v8.0.11,https://github.com/symfony/symfony.git - v7.4.11,https://github.com/symfony/symfony.git - v6.4.39
Step up your Open Source Security Game with Mend here