<?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 sightings.</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent sightings.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 19:22:23 +0000</lastBuildDate>
    <item>
      <title>0745f900-b6af-429f-9568-7f1ebbc6be56</title>
      <link>https://vulnerability.circl.lu/sighting/0745f900-b6af-429f-9568-7f1ebbc6be56/export</link>
      <description>{"uuid": "0745f900-b6af-429f-9568-7f1ebbc6be56", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mxick2qwid27", "content": "CVE-2026-108267 - go\nThe Privasys Go software, which adds special security checks to Go\u2019s TLS library, did not link the proof of a secure enclave to the actual network session in versions before v0.5.1-go1.26.5.\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#go #privasys #CVE #infosec", "creation_timestamp": "2026-10-10T01:10:06.512501Z"}</description>
      <content:encoded>{"uuid": "0745f900-b6af-429f-9568-7f1ebbc6be56", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://bsky.app/profile/stackflag.bsky.social/post/3mxick2qwid27", "content": "CVE-2026-108267 - go\nThe Privasys Go software, which adds special security checks to Go\u2019s TLS library, did not link the proof of a secure enclave to the actual network session in versions before v0.5.1-go1.26.5.\u2026\n\nToo many irrelevant or confusing CVEs? Use stackflag.com\n\n#go #privasys #CVE #infosec", "creation_timestamp": "2026-10-10T01:10:06.512501Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/0745f900-b6af-429f-9568-7f1ebbc6be56/export</guid>
      <pubDate>Sat, 10 Oct 2026 01:10:06 +0000</pubDate>
    </item>
    <item>
      <title>9fb1f662-66b5-446f-ae7e-5139fcfcd3bc</title>
      <link>https://vulnerability.circl.lu/sighting/9fb1f662-66b5-446f-ae7e-5139fcfcd3bc/export</link>
      <description>{"uuid": "9fb1f662-66b5-446f-ae7e-5139fcfcd3bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mxi727r7pn2o", "content": "\ud83d\udea8 CVE-2026-108267 \u2014 CVSS 9.1 CRITICAL\n\nPrivasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Pri...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-108267\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-10T00:07:33.371056Z"}</description>
      <content:encoded>{"uuid": "9fb1f662-66b5-446f-ae7e-5139fcfcd3bc", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://bsky.app/profile/stemshop.bsky.social/post/3mxi727r7pn2o", "content": "\ud83d\udea8 CVE-2026-108267 \u2014 CVSS 9.1 CRITICAL\n\nPrivasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Pri...\n\n\ud83d\udd0e https://stemshop.top/cve/CVE-2026-108267\n\n#CVE #CyberSecurity #InfoSec", "creation_timestamp": "2026-10-10T00:07:33.371056Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/9fb1f662-66b5-446f-ae7e-5139fcfcd3bc/export</guid>
      <pubDate>Sat, 10 Oct 2026 00:07:33 +0000</pubDate>
    </item>
    <item>
      <title>25e831b7-db2d-4a2a-9215-79e9975323ca</title>
      <link>https://vulnerability.circl.lu/sighting/25e831b7-db2d-4a2a-9215-79e9975323ca/export</link>
      <description>{"uuid": "25e831b7-db2d-4a2a-9215-79e9975323ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117413051196470510", "content": "CVE-2026-108267 Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Prior to privasys-v0.5.1-go1.26.5, challenge-mode RA-TLS certificates bound quote ReportData to the certificate public key and client nonce but not to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept a handshake terminated by the attacker as an attested enclave connection. This issue is fixed in privasys-v0.5.1-go1.26.5.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108267https://github.com/Privasys/go/security/advisories/GHSA-7jfw-53rm-phh2https://github.com/Privasys/go/commit/00a7d21ba53bba0ea09ac7a67eb2c6714e651700https://github.com/Privasys/go/releases/tag/privasys-v0.5.1-go1.26.5https://privasys.org/blog/binding-attestation-to-the-tls-session#privasys #Privasys #go#CVE_2026_108267#bot", "creation_timestamp": "2026-10-09T21:23:02.073418Z"}</description>
      <content:encoded>{"uuid": "25e831b7-db2d-4a2a-9215-79e9975323ca", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "9f56dd64-161d-43a6-b9c3-555944290a09", "vulnerability": "CVE-2026-108267", "type": "seen", "source": "https://infosec.exchange/users/cve/statuses/117413051196470510", "content": "CVE-2026-108267 Privasys Go fork: RA-TLS challenge mode did not bind attestation evidence to the TLS session Privasys Go is a maintained fork of the Go programming language that adds RA-TLS support to crypto/tls. Prior to privasys-v0.5.1-go1.26.5, challenge-mode RA-TLS certificates bound quote ReportData to the certificate public key and client nonce but not to the active TLS session. An attacker who obtained an enclave TLS private key could relay a genuine quote onto another connection, causing a relying party to accept a handshake terminated by the attacker as an attested enclave connection. This issue is fixed in privasys-v0.5.1-go1.26.5.\nhttps://www.cve.org/CVERecord?id=CVE-2026-108267https://github.com/Privasys/go/security/advisories/GHSA-7jfw-53rm-phh2https://github.com/Privasys/go/commit/00a7d21ba53bba0ea09ac7a67eb2c6714e651700https://github.com/Privasys/go/releases/tag/privasys-v0.5.1-go1.26.5https://privasys.org/blog/binding-attestation-to-the-tls-session#privasys #Privasys #go#CVE_2026_108267#bot", "creation_timestamp": "2026-10-09T21:23:02.073418Z"}</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/sighting/25e831b7-db2d-4a2a-9215-79e9975323ca/export</guid>
      <pubDate>Fri, 09 Oct 2026 21:23:02 +0000</pubDate>
    </item>
  </channel>
</rss>
