Most recent entries from all

cnvd-2020-29879

2026-10-09T04:50:00.600791+00:00

cnvd-2020-29879

EUVD-2026-36516

2026-10-09T04:50:00.600826+00:00

EUVD-2026-36516

fkie_cve-2020-5274

2026-10-09T04:50:00.600841+00:00

In Symfony before versions 5.0.5 and 4.4.5, some properties of the Exception were not properly escaped when the `ErrorHandler` rendered it stacktrace. In addition, the stacktrace were displayed even in a non-debug configuration. The ErrorHandler now escape alls properties of the exception, and the stacktrace is only display in debug configuration. This issue is patched in symfony/http-foundation versions 4.4.5 and 5.0.5

GHSA-m884-279h-32v2 — Exceptions displayed in non-debug configurations in Symfony

2026-10-09T04:50:00.600870+00:00

Affected: Packagist: symfony/error-handler, Packagist: symfony/symfony

Description -----------

When `ErrorHandler` renders an exception HTML page, it uses un-escaped properties from the related Exception class to render the stacktrace. The security issue comes from the fact that the stacktraces were also displayed in non-`debug` environments.

Resolution ----------

The `ErrorHandler` class now escapes all properties coming from the related Exception, and the stacktrace is not displayed anymore in non-`debug` environments.

The patches for this issue are available [here](https://github.com/symfony/symfony/commit/cf80224589ac05402d4f72f5ddf80900ec94d5ad) and [here](https://github.com/symfony/symfony/commit/629d21b800a15dc649fb0ae9ed7cd9211e7e45db) for branch 4.4.

Credits -------

I would like to thank Luka Sikic for reporting & Yonel Ceruto and Jérémy Derussé for fixing the issue.

gsd-2020-5274

2026-10-09T04:50:00.600906+00:00

gsd-2020-5274