Bug 2415751

Summary: CVE-2025-64500 nextcloud: Symfony HttpFoundation: Limited authorization bypass [fedora-41]
Product: [Fedora] Fedora Reporter: Jon Moroney <jmoroney>
Component: nextcloudAssignee: Andrew Bauer <zonexpertconsulting>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 41CC: ichavero, zonexpertconsulting
Target Milestone: ---Keywords: Security, SecurityTracking
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: {"flaws": ["d3c7e901-f5e2-4dbf-8116-134a268e432d"]}
Fixed In Version: nextcloud-32.0.2-1.fc44 nextcloud-32.0.2-1.el10_2 nextcloud-32.0.2-1.fc43 nextcloud-32.0.2-1.el10_1 nextcloud-32.0.2-1.fc42 nextcloud-32.0.2-1.fc41 Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-11-24 02:04:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2414695    

Description Jon Moroney 2025-11-18 21:38:50 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT.
https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams

Comment 1 Fedora Update System 2025-11-24 02:00:00 UTC
FEDORA-2025-7534523367 (nextcloud-32.0.2-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-7534523367

Comment 2 Fedora Update System 2025-11-24 02:04:18 UTC
FEDORA-2025-7534523367 (nextcloud-32.0.2-1.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2025-11-24 02:05:48 UTC
FEDORA-2025-84af4b9872 (nextcloud-32.0.2-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2025-84af4b9872

Comment 4 Fedora Update System 2025-11-24 02:05:48 UTC
FEDORA-EPEL-2025-f5ce86fd47 (nextcloud-32.0.2-1.el10_1) has been submitted as an update to Fedora EPEL 10.1.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f5ce86fd47

Comment 5 Fedora Update System 2025-11-24 02:05:49 UTC
FEDORA-EPEL-2025-12b5bcc5d5 (nextcloud-32.0.2-1.el10_2) has been submitted as an update to Fedora EPEL 10.2.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-12b5bcc5d5

Comment 6 Fedora Update System 2025-11-25 01:55:42 UTC
FEDORA-EPEL-2025-12b5bcc5d5 has been pushed to the Fedora EPEL 10.2 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-12b5bcc5d5

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2025-11-25 01:58:52 UTC
FEDORA-2025-84af4b9872 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-84af4b9872`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-84af4b9872

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 8 Fedora Update System 2025-11-25 02:02:51 UTC
FEDORA-EPEL-2025-f5ce86fd47 has been pushed to the Fedora EPEL 10.1 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-f5ce86fd47

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 9 Fedora Update System 2025-11-25 02:21:18 UTC
FEDORA-2025-f62aee4fe6 has been pushed to the Fedora 42 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-f62aee4fe6`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-f62aee4fe6

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 10 Fedora Update System 2025-11-25 03:20:33 UTC
FEDORA-2025-bb6c04e3ee has been pushed to the Fedora 41 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2025-bb6c04e3ee`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2025-bb6c04e3ee

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 11 Fedora Update System 2025-12-03 00:40:21 UTC
FEDORA-EPEL-2025-12b5bcc5d5 (nextcloud-32.0.2-1.el10_2) has been pushed to the Fedora EPEL 10.2 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 12 Fedora Update System 2025-12-03 00:52:23 UTC
FEDORA-2025-84af4b9872 (nextcloud-32.0.2-1.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 13 Fedora Update System 2025-12-03 00:55:27 UTC
FEDORA-EPEL-2025-f5ce86fd47 (nextcloud-32.0.2-1.el10_1) has been pushed to the Fedora EPEL 10.1 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 14 Fedora Update System 2025-12-03 01:05:45 UTC
FEDORA-2025-f62aee4fe6 (nextcloud-32.0.2-1.fc42) has been pushed to the Fedora 42 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 15 Fedora Update System 2025-12-03 01:35:46 UTC
FEDORA-2025-bb6c04e3ee (nextcloud-32.0.2-1.fc41) has been pushed to the Fedora 41 stable repository.
If problem still persists, please make note of it in this bug report.