Bug 2460584 - CVE-2026-6861 emacs: Emacs: Memory corruption vulnerability when processing SVG CSS [fedora-42]
Summary: CVE-2026-6861 emacs: Emacs: Memory corruption vulnerability when processing S...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 42
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Peter Oliver
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: {"flaws": ["96bd375f-348b-4a5a-a6fc-2...
Depends On:
Blocks: CVE-2026-6861
TreeView+ depends on / blocked
 
Reported: 2026-04-22 13:08 UTC by Avinash Hanwate
Modified: 2026-05-01 01:23 UTC (History)
8 users (show)

Fixed In Version: emacs-30.2-2.fc42
Clone Of:
Environment:
Last Closed: 2026-05-01 01:23:44 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Avinash Hanwate 2026-04-22 13:08:40 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-04-22 17:17:29 UTC
FEDORA-2026-52dad6273a (emacs-30.2-2.fc42) has been submitted as an update to Fedora 42.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-52dad6273a

Comment 2 Fedora Update System 2026-04-23 02:14:36 UTC
FEDORA-2026-52dad6273a 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-2026-52dad6273a`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-52dad6273a

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

Comment 3 Fedora Update System 2026-05-01 01:23:44 UTC
FEDORA-2026-52dad6273a (emacs-30.2-2.fc42) has been pushed to the Fedora 42 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.