Bug 2369707 - CVE-2025-49113 roundcubemail: From CVEorg collector [epel-9]
Summary: CVE-2025-49113 roundcubemail: From CVEorg collector [epel-9]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: roundcubemail
Version: epel9
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["5be30188-2ee7-48a7-bcfc-2...
Depends On:
Blocks: CVE-2025-49113
TreeView+ depends on / blocked
 
Reported: 2025-06-02 07:31 UTC by Michal Findra
Modified: 2025-06-11 00:58 UTC (History)
6 users (show)

Fixed In Version: roundcubemail-1.5.10-1.el9
Clone Of:
Environment:
Last Closed: 2025-06-11 00:58:33 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)

Description Michal Findra 2025-06-02 07:31:57 UTC 
More information about this security flaw is available in the following bug:

https://bugzilla.redhat.com/show_bug.cgi?id=2369696

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.
Comment 1 Fedora Update System 2025-06-02 07:59:02 UTC 
FEDORA-EPEL-2025-5c25fd8e2d (roundcubemail-1.5.10-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2025-5c25fd8e2d
Comment 2 Fedora Update System 2025-06-03 01:44:32 UTC 
FEDORA-EPEL-2025-5c25fd8e2d has been pushed to the Fedora EPEL 9 testing repository.

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

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Comment 3 Fedora Update System 2025-06-11 00:58:33 UTC 
FEDORA-EPEL-2025-5c25fd8e2d (roundcubemail-1.5.10-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.
Note You need to log in before you can comment on or make changes to this bug.