<?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://db.gcve.eu</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>Sat, 14 Nov 2026 07:18:57 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-40693</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-40693</link>
      <description>&lt;p&gt;Improper input validation for some Intel(R) TDX Workload Attestation software within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper input validation for some Intel(R) TDX Workload Attestation software within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-40693</guid>
    </item>
    <item>
      <title>GHSA-gwf2-8595-qw97</title>
      <link>https://db.gcve.eu/vuln/ghsa-gwf2-8595-qw97</link>
      <description>&lt;p&gt;Improper input validation for some Intel(R) TDX Workload Attestation software within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper input validation for some Intel(R) TDX Workload Attestation software within Ring 3: User Applications may allow a denial of service. Unprivileged software adversary with an authenticated user combined with a high complexity attack may enable denial of service. This result may potentially occur via local access when attack requirements are present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (none) and availability (none) impacts.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-gwf2-8595-qw97</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0480 — Panic on a GCP launch endorsement without TDX measurements</title>
      <link>https://db.gcve.eu/vuln/rustsec-2026-0480</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tdx_workload_attestation&lt;/p&gt;
&lt;p&gt;`GcpTdxHost::verify_launch_endorsement()`, available with the `host-gcp-tdx`
feature, read `uefi_golden.tdx.measurements[0]` without checking that the
golden measurement contains a TDX measurement. If a launch endorsement&amp;#39;s
golden measurement had no TDX measurements, the call panicked with an index
out of bounds instead of returning an error.&lt;/p&gt;
&lt;p&gt;The panic is reached only after the endorsement&amp;#39;s signing certificate and
signature have been verified. Triggering it therefore requires a correctly
signed endorsement that lacks TDX measurements.&lt;/p&gt;
&lt;p&gt;Intel describes the issue as improper input validation and classifies it as
denial of service, with a CVSS 4.0 base score of 5.7, in INTEL-SA-01520.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in
[#87](https://github.com/IntelLabs/tdx-workload-attestation/pull/87), released
in 0.2.0. The function now returns `Error::ParseError` when the TDX
measurement structure is missing or empty.&lt;/p&gt;
&lt;p&gt;Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: tdx_workload_attestation&lt;/p&gt;
&lt;p&gt;`GcpTdxHost::verify_launch_endorsement()`, available with the `host-gcp-tdx`
feature, read `uefi_golden.tdx.measurements[0]` without checking that the
golden measurement contains a TDX measurement. If a launch endorsement&amp;#39;s
golden measurement had no TDX measurements, the call panicked with an index
out of bounds instead of returning an error.&lt;/p&gt;
&lt;p&gt;The panic is reached only after the endorsement&amp;#39;s signing certificate and
signature have been verified. Triggering it therefore requires a correctly
signed endorsement that lacks TDX measurements.&lt;/p&gt;
&lt;p&gt;Intel describes the issue as improper input validation and classifies it as
denial of service, with a CVSS 4.0 base score of 5.7, in INTEL-SA-01520.&lt;/p&gt;
&lt;p&gt;The flaw was corrected in
[#87](https://github.com/IntelLabs/tdx-workload-attestation/pull/87), released
in 0.2.0. The function now returns `Error::ParseError` when the TDX
measurement structure is missing or empty.&lt;/p&gt;
&lt;p&gt;Reported by [Borys Tsyrulnikov](https://borystsyrulnikov.dev).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/rustsec-2026-0480</guid>
    </item>
  </channel>
</rss>
