CVE-2025-47278

{"dataType": "CVE_RECORD", "dataVersion": "5.1", "cveMetadata": {"cveId": "CVE-2025-47278", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "state": "PUBLISHED", "assignerShortName": "GitHub_M", "dateReserved": "2025-05-05T16:53:10.373Z", "datePublished": "2025-05-13T15:57:40.409Z", "dateUpdated": "2025-05-13T20:14:09.702Z"}, "containers": {"cna": {"title": "Flask uses fallback key instead of current signing key", "problemTypes": [{"descriptions": [{"cweId": "CWE-683", "lang": "en", "description": "CWE-683: Function Call With Incorrect Order of Arguments", "type": "CWE"}]}], "metrics": [{"cvssV4_0": {"attackVector": "LOCAL", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "userInteraction": "NONE", "vulnConfidentialityImpact": "NONE", "vulnIntegrityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "baseScore": 1.8, "baseSeverity": "LOW", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N", "version": "4.0"}}], "references": [{"name": "https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g", "tags": ["x_refsource_CONFIRM"], "url": "https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g"}, {"name": "https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09", "tags": ["x_refsource_MISC"], "url": "https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09"}, {"name": "https://github.com/pallets/flask/releases/tag/3.1.1", "tags": ["x_refsource_MISC"], "url": "https://github.com/pallets/flask/releases/tag/3.1.1"}], "affected": [{"vendor": "pallets", "product": "flask", "versions": [{"version": "= 3.1.0", "status": "affected"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2025-05-13T15:57:40.409Z"}, "descriptions": [{"lang": "en", "value": "Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the `itsdangerous` library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting `SECRET_KEY_FALLBACKS` care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue."}], "source": {"advisory": "GHSA-4grg-w6v8-c28g", "discovery": "UNKNOWN"}}, "adp": [{"metrics": [{"other": {"type": "ssvc", "content": {"timestamp": "2025-05-13T20:13:56.371838Z", "id": "CVE-2025-47278", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "role": "CISA Coordinator", "version": "2.0.3"}}}], "title": "CISA ADP Vulnrichment", "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2025-05-13T20:14:09.702Z"}}]}}

{"dataType": "CVE_RECORD", "containers": {"adp": [{"title": "CISA ADP Vulnrichment", "metrics": [{"other": {"type": "ssvc", "content": {"id": "CVE-2025-47278", "role": "CISA Coordinator", "options": [{"Exploitation": "none"}, {"Automatable": "no"}, {"Technical Impact": "partial"}], "version": "2.0.3", "timestamp": "2025-05-13T20:13:56.371838Z"}}}], "providerMetadata": {"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "shortName": "CISA-ADP", "dateUpdated": "2025-05-13T20:14:03.651Z"}}], "cna": {"title": "Flask uses fallback key instead of current signing key", "source": {"advisory": "GHSA-4grg-w6v8-c28g", "discovery": "UNKNOWN"}, "metrics": [{"cvssV4_0": {"version": "4.0", "baseScore": 1.8, "attackVector": "LOCAL", "baseSeverity": "LOW", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N", "userInteraction": "NONE", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "privilegesRequired": "HIGH", "subIntegrityImpact": "NONE", "vulnIntegrityImpact": "NONE", "subAvailabilityImpact": "NONE", "vulnAvailabilityImpact": "LOW", "subConfidentialityImpact": "NONE", "vulnConfidentialityImpact": "NONE"}}], "affected": [{"vendor": "pallets", "product": "flask", "versions": [{"status": "affected", "version": "= 3.1.0"}]}], "references": [{"url": "https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g", "name": "https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g", "tags": ["x_refsource_CONFIRM"]}, {"url": "https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09", "name": "https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09", "tags": ["x_refsource_MISC"]}, {"url": "https://github.com/pallets/flask/releases/tag/3.1.1", "name": "https://github.com/pallets/flask/releases/tag/3.1.1", "tags": ["x_refsource_MISC"]}], "descriptions": [{"lang": "en", "value": "Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the `itsdangerous` library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting `SECRET_KEY_FALLBACKS` care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue."}], "problemTypes": [{"descriptions": [{"lang": "en", "type": "CWE", "cweId": "CWE-683", "description": "CWE-683: Function Call With Incorrect Order of Arguments"}]}], "providerMetadata": {"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "shortName": "GitHub_M", "dateUpdated": "2025-05-13T15:57:40.409Z"}}}, "cveMetadata": {"cveId": "CVE-2025-47278", "state": "PUBLISHED", "dateUpdated": "2025-05-13T20:14:09.702Z", "dateReserved": "2025-05-05T16:53:10.373Z", "assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa", "datePublished": "2025-05-13T15:57:40.409Z", "assignerShortName": "GitHub_M"}, "dataVersion": "5.1"}

{"affected": [{"affectedData": [{"product": "flask", "vendor": "pallets", "versions": [{"status": "affected", "version": "= 3.1.0"}]}], "source": "security-advisories@github.com"}], "cveTags": [], "descriptions": [{"lang": "en", "value": "Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the `itsdangerous` library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting `SECRET_KEY_FALLBACKS` care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue."}, {"lang": "es", "value": "Flask es un framework de aplicaciones web con interfaz de puerta de enlace de servidor web (WSGI). En Flask 3.1.0, la configuraci\u00f3n de la clave de reserva hac\u00eda que se usara la \u00faltima clave de reserva para firmar, en lugar de la clave de firma actual. La librer\u00eda `itsdangerous` proporciona la firma. Se puede pasar una lista de claves, y Flask espera que la \u00faltima clave (la superior) sea la m\u00e1s reciente, utiliz\u00e1ndola para firmar. Sin embargo, Flask constru\u00eda incorrectamente esa lista a la inversa, pasando primero la clave de firma. Es probable que los sitios que hayan optado por la rotaci\u00f3n de claves mediante `SECRET_KEY_FALLBACKS` firmen inesperadamente sus sesiones con claves obsoletas, lo que dificultar\u00e1 la transici\u00f3n a claves m\u00e1s recientes. Las sesiones siguen firmadas, por lo que esto no causar\u00eda ninguna p\u00e9rdida de integridad de los datos. La versi\u00f3n 3.1.1 incluye un parche para este problema."}], "id": "CVE-2025-47278", "lastModified": "2026-06-17T09:27:39.367", "metrics": {"cvssMetricV40": [{"cvssData": {"Automatable": "NOT_DEFINED", "Recovery": "NOT_DEFINED", "Safety": "NOT_DEFINED", "attackComplexity": "LOW", "attackRequirements": "PRESENT", "attackVector": "LOCAL", "availabilityRequirement": "NOT_DEFINED", "baseScore": 1.8, "baseSeverity": "LOW", "confidentialityRequirement": "NOT_DEFINED", "exploitMaturity": "NOT_DEFINED", "integrityRequirement": "NOT_DEFINED", "modifiedAttackComplexity": "NOT_DEFINED", "modifiedAttackRequirements": "NOT_DEFINED", "modifiedAttackVector": "NOT_DEFINED", "modifiedPrivilegesRequired": "NOT_DEFINED", "modifiedSubAvailabilityImpact": "NOT_DEFINED", "modifiedSubConfidentialityImpact": "NOT_DEFINED", "modifiedSubIntegrityImpact": "NOT_DEFINED", "modifiedUserInteraction": "NOT_DEFINED", "modifiedVulnAvailabilityImpact": "NOT_DEFINED", "modifiedVulnConfidentialityImpact": "NOT_DEFINED", "modifiedVulnIntegrityImpact": "NOT_DEFINED", "privilegesRequired": "HIGH", "providerUrgency": "NOT_DEFINED", "subAvailabilityImpact": "NONE", "subConfidentialityImpact": "NONE", "subIntegrityImpact": "NONE", "userInteraction": "NONE", "valueDensity": "NOT_DEFINED", "vectorString": "CVSS:4.0/AV:L/AC:L/AT:P/PR:H/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X", "version": "4.0", "vulnAvailabilityImpact": "LOW", "vulnConfidentialityImpact": "NONE", "vulnIntegrityImpact": "NONE", "vulnerabilityResponseEffort": "NOT_DEFINED"}, "source": "security-advisories@github.com", "type": "Secondary"}], "ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-47278", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "role": "CISA Coordinator", "timestamp": "2025-05-13T20:13:56.371838Z", "version": "2.0.3"}}]}, "published": "2025-05-13T16:15:32.187", "references": [{"source": "security-advisories@github.com", "url": "https://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09"}, {"source": "security-advisories@github.com", "url": "https://github.com/pallets/flask/releases/tag/3.1.1"}, {"source": "security-advisories@github.com", "url": "https://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g"}], "sourceIdentifier": "security-advisories@github.com", "vulnStatus": "Deferred", "weaknesses": [{"description": [{"lang": "en", "value": "CWE-683"}], "source": "security-advisories@github.com", "type": "Secondary"}]}

{"bugzilla": {"description": "flask: Flask Session Signing Fallback Key Vulnerability", "id": "2365965", "url": "https://bugzilla.redhat.com/show_bug.cgi?id=2365965"}, "csaw": false, "cvss3": {"cvss3_base_score": "2.3", "cvss3_scoring_vector": "CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L", "status": "draft"}, "cwe": "CWE-683", "details": ["Flask is a web server gateway interface (WSGI) web application framework. In Flask 3.1.0, the way fallback key configuration was handled resulted in the last fallback key being used for signing, rather than the current signing key. Signing is provided by the `itsdangerous` library. A list of keys can be passed, and it expects the last (top) key in the list to be the most recent key, and uses that for signing. Flask was incorrectly constructing that list in reverse, passing the signing key first. Sites that have opted-in to use key rotation by setting `SECRET_KEY_FALLBACKS` care likely to unexpectedly be signing their sessions with stale keys, and their transition to fresher keys will be impeded. Sessions are still signed, so this would not cause any sort of data integrity loss. Version 3.1.1 contains a patch for the issue.", "A flaw was found in Flask. This vulnerability allows sessions to be signed with stale keys via incorrect fallback key configuration."], "name": "CVE-2025-47278", "package_state": [{"cpe": "cpe:/o:redhat:enterprise_linux:8", "fix_state": "Not affected", "package_name": "python-flask", "product_name": "Red Hat Enterprise Linux 8"}, {"cpe": "cpe:/a:redhat:openshift:4", "fix_state": "Not affected", "package_name": "python-flask", "product_name": "Red Hat OpenShift Container Platform 4"}, {"cpe": "cpe:/a:redhat:openstack:16.2", "fix_state": "Not affected", "package_name": "python-flask", "product_name": "Red Hat OpenStack Platform 16.2"}, {"cpe": "cpe:/a:redhat:openstack:17.1", "fix_state": "Not affected", "package_name": "python-flask", "product_name": "Red Hat OpenStack Platform 17.1"}, {"cpe": "cpe:/a:redhat:openstack:18.0", "fix_state": "Not affected", "package_name": "python-flask", "product_name": "Red Hat OpenStack Platform 18.0"}, {"cpe": "cpe:/a:redhat:quay:3", "fix_state": "Not affected", "package_name": "quay/quay-rhel8", "product_name": "Red Hat Quay 3"}], "public_date": "2025-05-13T15:57:40Z", "references": ["https://www.cve.org/CVERecord?id=CVE-2025-47278\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-47278\nhttps://github.com/pallets/flask/commit/73d6504063bfa00666a92b07a28aaf906c532f09\nhttps://github.com/pallets/flask/releases/tag/3.1.1\nhttps://github.com/pallets/flask/security/advisories/GHSA-4grg-w6v8-c28g"], "threat_severity": "Low"}

{}