symfony — security advisory
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login. It does so only in case the logged in user changes by means of checking the user identifier. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations, which is not the case at the moment. As of versions 5.4.31 and 6.3.8, Symfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.
- Products
- symfony
- Affected versions
- 5.4.23+dfsg-1
- Fixed versions
- 5.4.23+dfsg-1+deb12u1, 5.4.31+dfsg-1
- CVEs
- CVE-2023-46733
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 16:06 UTC · Revision 1
Source evidence
Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login. It does so only in case the logged in user changes by means of checking the user identifier. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations, which is not the case at the moment. As of versions 5.4.31 and 6.3.8, Symfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.
osv:DEBIAN-CVE-2023-46733
symfony
Fixed versions: 5.4.23+dfsg-1+deb12u1
symfony
Fixed versions: 5.4.31+dfsg-1
symfony
Fixed versions: 5.4.31+dfsg-1
Complete source record
{
"id": "b8b747d23a66659196e29e853b09952f2d9c80f4d7b839c940d7af73f9e7f913",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2023-46733",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2023-46733",
"summary": "Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login. It does so only in case the logged in user changes by means of checking the user identifier. In some use cases, the user identifier doesn't change between the verification phase and the successful login, while the token itself changes from one type (partially-authenticated) to another (fully-authenticated). When this happens, the session id should be regenerated to prevent possible session fixations, which is not the case at the moment. As of versions 5.4.31 and 6.3.8, Symfony now checks the type of the token in addition to the user identifier before deciding whether the session id should be regenerated.",
"evidence": "osv:DEBIAN-CVE-2023-46733",
"products": [
{
"name": {
"value": "symfony",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.23+dfsg-1+deb12u1",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": [
{
"value": "5.4.23+dfsg-1",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "symfony",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.31+dfsg-1",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "symfony",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "5.4.31+dfsg-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "DEBIAN-CVE-2023-46733",
"aliases": [
"DEBIAN-CVE-2023-46733"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.23+dfsg-1+deb12u1"
}
]
}
],
"package": {
"name": "symfony",
"purl": "pkg:deb/debian/symfony?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"5.4.23+dfsg-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-46733.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.31+dfsg-1"
}
]
}
],
"package": {
"name": "symfony",
"purl": "pkg:deb/debian/symfony?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-46733.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "5.4.31+dfsg-1"
}
]
}
],
"package": {
"name": "symfony",
"purl": "pkg:deb/debian/symfony?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2023-46733.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-26T18:02:42.247486083Z",
"provider": "osv",
"upstream": [
"CVE-2023-46733"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2023-46733"
]
},
"related_cves": [
{
"value": "CVE-2023-46733",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 456640,
"published_at": "2023-11-10T18:15:09.05+00:00"
}