<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-29T06:32:27.999692+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/fkie_cve-2026-45057</id>
    <title>fkie_cve-2026-45057</title>
    <updated>2026-09-29T06:32:28.047247+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>matrix-sdk-ui provides GUI-centric utilities on top of matrix-rust-sdk. The message edit validation logic in the  `matrix-sdk-ui` crate prior to 0.17.0 is missing a check: when replacing an encrypted event, the replacement event itself is not required to be encrypted. This enables a malicious homeserver administrators (or actors with equivalent power) to impersonate or spoof messages as if they were sent by a victim user. `matrix-sdk-ui` 0.17.0 fixes the message edit validation logic to align with the algorithm for replacement events[^1] described in the Matrix specification. No known workarounds are available.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-45057"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-h97m-27fx-42rx</id>
    <title>GHSA-h97m-27fx-42rx — matrix-sdk-ui: Incomplete edit validation</title>
    <updated>2026-09-29T06:32:28.047346+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: matrix-sdk-ui</p>
<p>### Impact
The message edit validation logic in the  `matrix-sdk-ui` crate before 0.16.1 is missing a check: when replacing an encrypted event, the replacement event itself is not required to be encrypted. This enables a malicious homeserver administrator (or an actor with equivalent power) to impersonate or spoof messages as if they were sent by a victim user.</p>
<p>### Patches
`matrix-sdk-ui` 0.16.1 fixes the message edit validation logic to align with the algorithm for replacement events[^1] described in the Matrix specification.</p>
<p>### Workarounds
N/A</p>
<p>### References
* Pull request: https://github.com/matrix-org/matrix-rust-sdk/pull/6454</p>
<p>### For more information
If you have any questions or comments about this advisory, please email us at [security at matrix.org](mailto:security@matrix.org).</p>
<p>[^1]: https://spec.matrix.org/unstable/client-server-api/#validity-of-replacement-events</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-h97m-27fx-42rx"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rustsec-2026-0158</id>
    <title>RUSTSEC-2026-0158 — Incomplete message edit validation in matrix-sdk-ui</title>
    <updated>2026-09-29T06:32:28.047417+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: matrix-sdk-ui</p>
<p>The message edit validation logic in the matrix-sdk-ui crate before 0.16.1 is
missing a check: when replacing an encrypted event, the replacement event itself
is not required to be encrypted. This enables a malicious homeserver
administrator (or an actor with equivalent power) to impersonate or spoof
messages as if they were sent by a victim user.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rustsec-2026-0158"/>
  </entry>
</feed>
