# CVE-2026-46529: PDF /GoToR action argv injection enables single-click RCE via --gtk-module dlopen > Attackers can achieve remote code execution by tricking users into clicking a malicious PDF link, exploiting command line injection in Atril. - **Severity:** High 8.4 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 10 Jun 2026 - **Updated:** 28 Jul 2026 - **Also known as:** ALSA-2026:27819, ALSA-2026:28998, CLSA-2026-1782485183, CLSA-2026-1782819496, DEBIAN-CVE-2026-46529, GHSA-vgv2-m826-8f6f, MGASA-2026-0209, OESA-2026-2766, RHSA-2026:27819, RHSA-2026:28998, RHSA-2026:33169, RHSA-2026:33416, RHSA-2026:39115, RHSA-2026:41904, RHSA-2026:42692, RHSA-2026:43398, RHSA-2026:46467, RLSA-2026:27819, RLSA-2026:28998, SUSE-SU-2026:22182-1, SUSE-SU-2026:2232-1, SUSE-SU-2026:2235-1, SUSE-SU-2026:2288-1, UBUNTU-CVE-2026-46529, USN-8295-1, USN-8321-1, openSUSE-SU-2026:10853-1, openSUSE-SU-2026:11163-1, openSUSE-SU-2026:20850-1, openSUSE-SU-2026:21106-1 ## What is CVE-2026-46529? CVE-2026-46529 is a high-severity command injection vulnerability in mate-desktop atril, published on 10 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description Atril Document Viewer is the default document reader of the MATE desktop environment for Linux. A single-click remote code execution vulnerability in versions prior to 1.26.3 and 1.28.4 allows an attacker to achieve arbitrary code execution as the user by tricking them into clicking a link inside a malicious PDF document. The PDF can be packaged as a polyglot file that is simultaneously a valid PDF and a valid ELF shared library, making the attack a single-file, single-click, configuration-independent RCE on stock atril installations. The root cause is `shell/ev-application.c:ev_spawn`, which builds a command line from attacker-controlled PDF link-destination fields without applying `g_shell_quote`. The cmdline is then handed to `g_app_info_create_from_commandline`, which shell-parses it back into argv — splitting any embedded `--gtk-module=PATH` into a separate argv element. GTK then `dlopen()`s the path during init, running any `__attribute__((constructor))` it finds. Versions 1.26.3 and 1.28.4 contain a patch for the issue. This is the same defect class as CVE-2023-51698 (CBT `--checkpoint-action` injection in `comics-document.c`, fixed in 1.6.2) but in a different code path (`shell/ev-application.c`) that the original patch did not touch. Weakness: CWE-88 (Improper Neutralization of Argument Delimiters in a Command), CWE-829 (Inclusion of Functionality from Untrusted Control Sphere), CWE-77 (Improper Neutralization of Special Elements used in a Command) ## Which versions are affected by CVE-2026-46529? | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `evince` | AlmaLinux:8 | All versions | 3.28.4-17.el8_10 | | `evince-browser-plugin` | AlmaLinux:8 | All versions | 3.28.4-17.el8_10 | | `evince-devel` | AlmaLinux:8 | All versions | 3.28.4-17.el8_10 | | `evince-libs` | AlmaLinux:8 | All versions | 3.28.4-17.el8_10 | | `evince-nautilus` | AlmaLinux:8 | All versions | 3.28.4-17.el8_10 | | `evince` | AlmaLinux:9 | All versions | 40.5-4.el9_8.1 | | `evince-libs` | AlmaLinux:9 | All versions | 40.5-4.el9_8.1 | | `evince-nautilus` | AlmaLinux:9 | All versions | 40.5-4.el9_8.1 | | `evince-previewer` | AlmaLinux:9 | All versions | 40.5-4.el9_8.1 | | `evince-thumbnailer` | AlmaLinux:9 | All versions | 40.5-4.el9_8.1 | | `evince` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-browser-plugin` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-browser-plugin-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-libs` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-libs-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-nautilus` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-nautilus-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.28.4-17.el8_10 | | `evince-browser-plugin-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince-debugsource` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince-devel` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince-libs-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince-nautilus-debuginfo` | Red Hat:enterprise_linux:8::crb | All versions | 0:3.28.4-17.el8_10 | | `evince` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-dvi-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-libs` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-libs-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-nautilus` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-nautilus-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-previewer` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-previewer-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-thumbnailer` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince-thumbnailer-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:40.5-4.el9_8.1 | | `evince` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.28.4-11.el8_4.1 | | `evince-browser-plugin` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.28.4-11.el8_4.1 | | `evince-browser-plugin-debuginfo` | Red Hat:rhel_aus:8.4::appstream | All versions | 0:3.28.4-11.el8_4.1 | ## How do I fix CVE-2026-46529? Apply the vendor's patch. ## Is CVE-2026-46529 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46529 exists. Public exploit code: - Evince/xreader/Atril RCE exploit to CVE-2026-46529 (github_poc): https://github.com/N1et/CVE-2026-46529 ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46529 and fix it if it is affected. What it is: CVE-2026-46529 is a high-severity command injection vulnerability in mate-desktop atril, published on 10 Jun 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-46529 exists. Affected product: mate-desktop atril. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-46529/ (Markdown: https://insights.sbomify.com/CVE-2026-46529/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46529 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46529 - OSV: https://osv.dev/vulnerability/CVE-2026-46529 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46529/ Summaries are generated and may contain mistakes; the official description above is the record.