<?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-03T04:46:39.911058+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-55549</id>
    <title>fkie_cve-2026-55549</title>
    <updated>2026-10-03T04:46:39.934706+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Yamcs is a mission control framework. Prior to 5.9.4, Yamcs reflects an attacker-controlled redirect_uri parameter from GET /auth/authorize into yamcs-core/src/main/resources/auth/templates/authorize.html without adequate HTML escaping by yamcs-core/src/main/java/org/yamcs/http/auth/AuthHandler.java and yamcs-core/src/main/java/org/yamcs/http/HandlerContext.java. A crafted authorization URL can execute JavaScript when opened by a Yamcs user. The script can access browser-held authentication material and transmit it to an attacker, enabling account compromise. This issue is fixed in version 5.9.4.</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/fkie_cve-2026-55549"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-rxpg-wjf8-qv9c</id>
    <title>GHSA-rxpg-wjf8-qv9c — Yamcs has Reflected XSS in the URL of the Authorize Endpoint</title>
    <updated>2026-10-03T04:46:39.934790+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.yamcs:yamcs-core</p>
<p>### Attack type: 
Unauthenticated remote</p>
<p>### Impact: 
Attackers can execute arbitrary JavaScript in a user's browser, including obtaining a user's session token and refresh token.</p>
<p>### Affected components: authorize.html, AuthHandler.java, HandlerContext.java</p>
<p>A Reflected Cross-Site Scripting vulnerability exists in Yamcs &lt;=5.8.6, allowing an attacker to execute arbitrary JavaScript in a Yamcs user's browser. This vulnerability can be exploited to exfiltrate a logged-in user's access token and send it to a remote server, leading to the takeover of the user's account.</p>
<p>Using a specially crafted URL, you are able to execute a JavaScript `alert()` call in the browser:</p>
<p>&lt;img width="1794" height="816" alt="image" src="https://github.com/user-attachments/assets/4a5b6aa4-bceb-4b3d-bc5d-3dac0895ff2e" /&gt;</p>
<p>You then use JavaScript to obtain the user's cookies and display them in the alert:</p>
<p>&lt;img width="1794" height="1290" alt="image" src="https://github.com/user-attachments/assets/6c6d2837-db77-409a-a66d-0d2e4edd5435" /&gt;</p>
<p>Finally, use the `fetch` function to send the user's cookies to a remote server which we controlled:</p>
<p>&lt;img width="2370" height="1025" alt="image" src="https://github.com/user-attachments/assets/2989fc79-6ca0-4256-afc4-71d44d9923b8" /&gt;</p>
<p>Now you can set these cookies in our own browser and login to Yamcs as the user.</p>
<p>## Steps to Reproduce
1. Start Yamcs
2. Login as a user
3. In a terminal, start a netcat listener:</p>
<p>```
nc -nlvp 8888
```</p>
<p>4. Paste the following URL p…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-rxpg-wjf8-qv9c"/>
  </entry>
</feed>
