<?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-10-09T03:33:35.468298+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-2008-5555</id>
    <title>fkie_cve-2008-5555</title>
    <updated>2026-10-09T03:33:36.367728+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Microsoft Internet Explorer 8.0 Beta 2 relies on the XDomainRequestAllowed HTTP header to authorize data exchange between domains, which allows remote attackers to bypass the product's XSS Filter protection mechanism, and conduct XSS and cross-domain attacks, by injecting this header after a CRLF sequence, related to "XDomainRequest Allowed Injection (XAI)." NOTE: the vendor has reportedly stated that the XSS Filter intentionally does not attempt to "address every conceivable XSS attack scenario."</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2008-5555"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-vfp4-vxgp-j26v</id>
    <title>GHSA-vfp4-vxgp-j26v</title>
    <updated>2026-10-09T03:33:36.367837+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Microsoft Internet Explorer 8.0 Beta 2 relies on the XDomainRequestAllowed HTTP header to authorize data exchange between domains, which allows remote attackers to bypass the product's XSS Filter protection mechanism, and conduct XSS and cross-domain attacks, by injecting this header after a CRLF sequence, related to "XDomainRequest Allowed Injection (XAI)." NOTE: the vendor has reportedly stated that the XSS Filter intentionally does not attempt to "address every conceivable XSS attack scenario."</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-vfp4-vxgp-j26v"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/gsd-2008-5555</id>
    <title>gsd-2008-5555</title>
    <updated>2026-10-09T03:33:36.367878+00:00</updated>
    <content>gsd-2008-5555</content>
    <link href="https://vulnerability.circl.lu/vuln/gsd-2008-5555"/>
  </entry>
</feed>
