[!IMPORTANT] This report is intentionally sanitized for public GitHub publication. Sensitive identifiers, credentials, infrastructure values, and client-specific evidence are replaced with clear placeholders.

🧭 Quick Navigation

• Executive Summary
• Technical Analysis
• Impact
• Remediation
• Lessons Learned & Mitigation Strategy

[!TIP] For a fast review, start with the Executive Summary and Impact sections. For technical depth, continue into Technical Analysis and Remediation.

🏷️ Title

CVE-2026-46529 - Atril Evince XReader PDF Clickable Link RCE

🧾 Executive Summary

ثغرة أمنية خطيرة من نوع تنفيذ أوامر عن بُعد بنقرة واحدة (Single-Click RCE) في عارض مستندات Atril (عارض PDF الافتراضي لبيئة MATE Desktop) وأخويه Evince (عارض GNOME) و XReader (عارض Xfce). تسمح هذه الثغرة لمهاجم بتنفيذ أكواد ضارة على جهاز الضحية بمجرد خداعه للنقر على رابط داخل ملف PDF.

تعمل الثغرة عن طريق تضمين رابط خبيث في مستند PDF. عند النقر على الرابط، يقوم التطبيق بتفسير URI بطريقة غير آمنة، مما يسمح بتنفيذ أوامر عشوائية بصلاحيات المستخدم الحالي.

🔬 Technical Analysis

The weakness was assessed from an application-security and infrastructure-risk perspective. The core issue is classified as Remote Code Execution and was documented in a sanitized form suitable for public portfolio publication.

تستغل الثغرة معالجة الروابط (URI Handling) في عارض المستندات Atril. عند النقر على رابط داخل مستند PDF، يقوم Atril بتمرير URI إلى النظام لفتحه. نظراً لعدم وجود تنقية كافية للروابط، يمكن للمهاجم إنشاء رابط باستخدام بروتوكولات خطيرة مثل file:// أو ghelp:// أو حتى تنفيذ أوامر مباشرة.

📊 Impact

• Unauthorized command execution within the affected application context.
• Potential service takeover, data exposure, and lateral movement depending on deployment privileges.

🛠️ Remediation

🧠 Lessons Learned & Mitigation Strategy

• Treat every integration boundary as untrusted, especially when application logic forwards user-controlled values to filesystems, shells, parsers, or external tools.
• Security reviews should validate the complete exploit chain, not only the first vulnerable endpoint; low-severity misconfigurations can become critical when chained.
• Public-facing documentation should describe risk, root cause, and remediation without exposing operational identifiers, credentials, or reusable exploitation artifacts.
• Defensive controls should combine preventive validation, runtime least privilege, telemetry, and patch governance to reduce both exploitability and blast radius.

🧼 Publication Sanitization Notes

• Sensitive infrastructure identifiers, IP addresses, hostnames, credentials, hashes, and e-mail addresses were replaced with explicit placeholders.
• Reusable operational evidence was minimized or abstracted to keep the document suitable for public GitHub publication.
• The document uses a consultant-style structure aligned with common web security testing report practices such as OWASP WSTG reporting expectations.