<?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>Mon, 05 Oct 2026 04:13:18 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-81697 — openssl_encrypt before 1.4.9 KDF Downgrade via CWD-relative Configuration</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-81697</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jahlives openssl_encrypt&lt;/p&gt;
&lt;p&gt;openssl_encrypt (pip package openssl-encrypt) versions &amp;lt;= 1.4.8 contain a CWD-relative configuration file resolution flaw in crypt_settings.py, where CONFIG_FILE (originally the absolute per-user path ~/.crypt_settings.json) is reassigned at line 84 to the bare relative name &amp;#39;crypt_settings.json&amp;#39;. As a result, the legacy Tk GUI&amp;#39;s SettingsTab reads and writes KDF settings from crypt_settings.json in the process launch (current working) directory instead of the user&amp;#39;s home directory. An attacker who plants a malicious crypt_settings.json (e.g. sha256:1 with all memory-hard KDFs disabled) can silently downgrade encryption performed in that GUI session to roughly one hash round, bypassing the weak-KDF preflight and enabling offline brute-force attacks against the resulting ciphertext. Fixed in 1.4.9.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; jahlives openssl_encrypt&lt;/p&gt;
&lt;p&gt;openssl_encrypt (pip package openssl-encrypt) versions &amp;lt;= 1.4.8 contain a CWD-relative configuration file resolution flaw in crypt_settings.py, where CONFIG_FILE (originally the absolute per-user path ~/.crypt_settings.json) is reassigned at line 84 to the bare relative name &amp;#39;crypt_settings.json&amp;#39;. As a result, the legacy Tk GUI&amp;#39;s SettingsTab reads and writes KDF settings from crypt_settings.json in the process launch (current working) directory instead of the user&amp;#39;s home directory. An attacker who plants a malicious crypt_settings.json (e.g. sha256:1 with all memory-hard KDFs disabled) can silently downgrade encryption performed in that GUI session to roughly one hash round, bypassing the weak-KDF preflight and enabling offline brute-force attacks against the resulting ciphertext. Fixed in 1.4.9.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-81697</guid>
    </item>
  </channel>
</rss>
