Bug 2489262 - CVE-2026-41149 nextcloud: Mermaid: HTML injection via classDef directive in state diagrams [fedora-all]
Summary: CVE-2026-41149 nextcloud: Mermaid: HTML injection via classDef directive in s...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: nextcloud
Version: rawhide
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Andrew Bauer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["caa24790-080f-40db-87e5-1...
Depends On:
Blocks: CVE-2026-41149
TreeView+ depends on / blocked
 
Reported: 2026-06-16 14:05 UTC by Ganesh
Modified: 2026-07-05 01:09 UTC (History)
2 users (show)

Fixed In Version: nextcloud-33.0.6-1.el10_2 nextcloud-33.0.6-1.fc43 nextcloud-33.0.6-1.el10_3 nextcloud-33.0.6-1.fc44
Clone Of:
Environment:
Last Closed: 2026-07-05 00:45:31 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ganesh 2026-06-16 14:05:26 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.

Comment 1 Fedora Update System 2026-06-26 20:14:23 UTC
FEDORA-2026-ee50c21f92 (nextcloud-33.0.6-1.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-ee50c21f92

Comment 2 Fedora Update System 2026-06-27 01:32:37 UTC
FEDORA-EPEL-2026-32625d66b9 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-2026-32625d66b9

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

Comment 3 Fedora Update System 2026-06-27 01:44:02 UTC
FEDORA-EPEL-2026-ba0c05aa3d has been pushed to the Fedora EPEL 10.3 testing repository.

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

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

Comment 4 Fedora Update System 2026-06-27 01:46:42 UTC
FEDORA-2026-5afe6630dc 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-2026-5afe6630dc`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-5afe6630dc

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

Comment 5 Fedora Update System 2026-06-27 01:59:56 UTC
FEDORA-2026-ee50c21f92 has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-ee50c21f92`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-ee50c21f92

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

Comment 6 Fedora Update System 2026-07-05 00:45:31 UTC
FEDORA-EPEL-2026-32625d66b9 (nextcloud-33.0.6-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 7 Fedora Update System 2026-07-05 00:51:31 UTC
FEDORA-2026-5afe6630dc (nextcloud-33.0.6-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 8 Fedora Update System 2026-07-05 01:00:02 UTC
FEDORA-EPEL-2026-ba0c05aa3d (nextcloud-33.0.6-1.el10_3) has been pushed to the Fedora EPEL 10.3 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2026-07-05 01:09:17 UTC
FEDORA-2026-ee50c21f92 (nextcloud-33.0.6-1.fc44) has been pushed to the Fedora 44 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.