<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 02 Oct 2026 19:34:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-10613</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-10613</link>
      <description>bdu:2024-10613</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-10613</guid>
    </item>
    <item>
      <title>EUVD-2026-205253</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-205253</link>
      <description>EUVD-2026-205253</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-205253</guid>
    </item>
    <item>
      <title>fkie_cve-2024-52800</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-52800</link>
      <description>&lt;p&gt;veraPDF is an open source PDF/A validation library. Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability. This doesn&amp;#39;t affect the standard validation and policy checks functionality, veraPDF&amp;#39;s common use cases. Most veraPDF users don&amp;#39;t insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust. This issue has not yet been patched. Users are advised to be cautious of XSLT code until a patch is available.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;veraPDF is an open source PDF/A validation library. Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability. This doesn&amp;#39;t affect the standard validation and policy checks functionality, veraPDF&amp;#39;s common use cases. Most veraPDF users don&amp;#39;t insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust. This issue has not yet been patched. Users are advised to be cautious of XSLT code until a patch is available.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-52800</guid>
    </item>
    <item>
      <title>GHSA-4cx5-89vm-833x — veraPDF CLI has potential XXE (XML External Entity Injection) vulnerability</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4cx5-89vm-833x</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.verapdf:core, Maven: org.verapdf:core-jakarta, Maven: org.verapdf:core-arlington, Maven: org.verapdf:verapdf-library, Maven: org.verapdf:verapdf-library-jakarta, Maven: org.verapdf:verapdf-library-arlington, Maven: org.verapdf:library, Maven: org.verapdf:library-jakarta, Maven: org.verapdf:library-arlington&lt;/p&gt;
&lt;p&gt;### Impact
Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability.&lt;/p&gt;
&lt;p&gt;### Patches
We are currently working on a patch that will be released when ready.&lt;/p&gt;
&lt;p&gt;### Workarounds
This doesn&amp;#39;t affect the standard validation and policy checks functionality, veraPDF&amp;#39;s common use cases. Most veraPDF users don&amp;#39;t insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust.&lt;/p&gt;
&lt;p&gt;### References
Original issue: #1488&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.verapdf:core, Maven: org.verapdf:core-jakarta, Maven: org.verapdf:core-arlington, Maven: org.verapdf:verapdf-library, Maven: org.verapdf:verapdf-library-jakarta, Maven: org.verapdf:verapdf-library-arlington, Maven: org.verapdf:library, Maven: org.verapdf:library-jakarta, Maven: org.verapdf:library-arlington&lt;/p&gt;
&lt;p&gt;### Impact
Executing policy checks using custom schematron files via the CLI invokes an XSL transformation that may theoretically lead to a remote code execution (RCE) vulnerability.&lt;/p&gt;
&lt;p&gt;### Patches
We are currently working on a patch that will be released when ready.&lt;/p&gt;
&lt;p&gt;### Workarounds
This doesn&amp;#39;t affect the standard validation and policy checks functionality, veraPDF&amp;#39;s common use cases. Most veraPDF users don&amp;#39;t insert any custom XSLT code into policy profiles, which are based on Schematron syntax rather than direct XSL transforms. For users who do, only load custom policy files from sources you trust.&lt;/p&gt;
&lt;p&gt;### References
Original issue: #1488&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4cx5-89vm-833x</guid>
    </item>
  </channel>
</rss>
