OESA-2026-2766 (CVE-2026-46529)

Vulnerability from osv_openeuler – Published: 2026-06-24 11:11 – Updated: 2026-08-06 11:11 – Source website
VLAI
Summary
evince security update
Details

Evince is a document viewer for multiple document formats. The goal of evince is to replace the multiple document viewers that exist on the GNOME Desktop with a single simple application. Evince is specifically designed to support the file following formats: PDF, Postscript, djvu, tiff, dvi, XPS, SyncTex support with gedit, comics books (cbr,cbz,cb7 and cbt).

Security Fix(es):

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.(CVE-2026-46529)


{
  "affected": [
    {
      "ecosystem_specific": {
        "aarch64": [
          "evince-3.30.1-5.oe2003sp4.aarch64.rpm",
          "evince-debuginfo-3.30.1-5.oe2003sp4.aarch64.rpm",
          "evince-debugsource-3.30.1-5.oe2003sp4.aarch64.rpm",
          "evince-devel-3.30.1-5.oe2003sp4.aarch64.rpm",
          "evince-help-3.30.1-5.oe2003sp4.aarch64.rpm"
        ],
        "src": [
          "evince-3.30.1-5.oe2003sp4.src.rpm"
        ],
        "x86_64": [
          "evince-3.30.1-5.oe2003sp4.x86_64.rpm",
          "evince-debuginfo-3.30.1-5.oe2003sp4.x86_64.rpm",
          "evince-debugsource-3.30.1-5.oe2003sp4.x86_64.rpm",
          "evince-devel-3.30.1-5.oe2003sp4.x86_64.rpm",
          "evince-help-3.30.1-5.oe2003sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:20.03-LTS-SP4",
        "name": "evince",
        "purl": "pkg:rpm/openEuler/evince\u0026distro=openEuler-20.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.30.1-5.oe2003sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "evince-3.38.2-2.oe2203sp4.aarch64.rpm",
          "evince-debuginfo-3.38.2-2.oe2203sp4.aarch64.rpm",
          "evince-debugsource-3.38.2-2.oe2203sp4.aarch64.rpm",
          "evince-devel-3.38.2-2.oe2203sp4.aarch64.rpm",
          "evince-help-3.38.2-2.oe2203sp4.aarch64.rpm"
        ],
        "src": [
          "evince-3.38.2-2.oe2203sp4.src.rpm"
        ],
        "x86_64": [
          "evince-3.38.2-2.oe2203sp4.x86_64.rpm",
          "evince-debuginfo-3.38.2-2.oe2203sp4.x86_64.rpm",
          "evince-debugsource-3.38.2-2.oe2203sp4.x86_64.rpm",
          "evince-devel-3.38.2-2.oe2203sp4.x86_64.rpm",
          "evince-help-3.38.2-2.oe2203sp4.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:22.03-LTS-SP4",
        "name": "evince",
        "purl": "pkg:rpm/openEuler/evince\u0026distro=openEuler-22.03-LTS-SP4"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "3.38.2-2.oe2203sp4"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "evince-44.3-3.oe2403sp1.aarch64.rpm",
          "evince-debuginfo-44.3-3.oe2403sp1.aarch64.rpm",
          "evince-debugsource-44.3-3.oe2403sp1.aarch64.rpm",
          "evince-devel-44.3-3.oe2403sp1.aarch64.rpm"
        ],
        "noarch": [
          "evince-help-44.3-3.oe2403sp1.noarch.rpm"
        ],
        "src": [
          "evince-44.3-3.oe2403sp1.src.rpm"
        ],
        "x86_64": [
          "evince-44.3-3.oe2403sp1.x86_64.rpm",
          "evince-debuginfo-44.3-3.oe2403sp1.x86_64.rpm",
          "evince-debugsource-44.3-3.oe2403sp1.x86_64.rpm",
          "evince-devel-44.3-3.oe2403sp1.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP1",
        "name": "evince",
        "purl": "pkg:rpm/openEuler/evince\u0026distro=openEuler-24.03-LTS-SP1"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "44.3-3.oe2403sp1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    },
    {
      "ecosystem_specific": {
        "aarch64": [
          "evince-44.3-3.oe2403sp3.aarch64.rpm",
          "evince-debuginfo-44.3-3.oe2403sp3.aarch64.rpm",
          "evince-debugsource-44.3-3.oe2403sp3.aarch64.rpm",
          "evince-devel-44.3-3.oe2403sp3.aarch64.rpm"
        ],
        "noarch": [
          "evince-help-44.3-3.oe2403sp3.noarch.rpm"
        ],
        "src": [
          "evince-44.3-3.oe2403sp3.src.rpm"
        ],
        "x86_64": [
          "evince-44.3-3.oe2403sp3.x86_64.rpm",
          "evince-debuginfo-44.3-3.oe2403sp3.x86_64.rpm",
          "evince-debugsource-44.3-3.oe2403sp3.x86_64.rpm",
          "evince-devel-44.3-3.oe2403sp3.x86_64.rpm"
        ]
      },
      "package": {
        "ecosystem": "openEuler:24.03-LTS-SP3",
        "name": "evince",
        "purl": "pkg:rpm/openEuler/evince\u0026distro=openEuler-24.03-LTS-SP3"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "44.3-3.oe2403sp3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "database_specific": {
    "severity": "High"
  },
  "details": "Evince is a document viewer for multiple document formats. The goal of evince is to replace the multiple document viewers that exist on the GNOME Desktop with a single simple application. Evince is specifically designed to support the file following formats: PDF, Postscript, djvu, tiff, dvi, XPS, SyncTex support with gedit, comics books (cbr,cbz,cb7 and cbt).\r\n\r\nSecurity Fix(es):\n\nAtril 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 \u2014 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.(CVE-2026-46529)",
  "id": "OESA-2026-2766",
  "modified": "2026-08-06T11:11:41Z",
  "published": "2026-06-24T11:11:41Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://www.openeuler.org/zh/security/security-bulletins/detail/?id=openEuler-SA-2026-2766"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-46529"
    }
  ],
  "schema_version": "1.7.2",
  "severity": [
    {
      "score": "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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X",
      "type": "CVSS_V4"
    }
  ],
  "summary": "evince security update",
  "upstream": [
    "CVE-2026-46529"
  ]
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Events included in the timeline

Loading timeline…


    Loading…

    Loading…

    Loading…

    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.