<?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-30T00:44:21.221306+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/cve-2026-25136</id>
    <title>CVE-2026-25136 — Rucio WebUI has a Reflected Cross-site Scripting Vulnerability</title>
    <updated>2026-09-30T00:44:21.295659+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> rucio</p>
<p>Rucio is a software framework that provides functionality to organize, manage, and access large volumes of scientific data using customizable policies. A reflected Cross-site Scripting vulnerability was located in versions prior to 35.8.3, 38.5.4, and 39.3.1 in the rendering of the ExceptionMessage of the WebUI 500 error which could allow attackers to steal login session tokens of users who navigate to a specially crafted URL. Versions 35.8.3, 38.5.4, and 39.3.1 fix the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-25136"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/ghsa-h79m-5jjm-jm4q</id>
    <title>GHSA-h79m-5jjm-jm4q — Rucio WebUI has a Reflected Cross-site Scripting Vulnerability</title>
    <updated>2026-09-30T00:44:21.295793+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: rucio-webui</p>
<p>### Summary
A reflected Cross-site Scripting vulnerability was located in the rendering of the ExceptionMessage of the WebUI 500 error which could allow attackers to steal login session tokens of users who navigate to a specially crafted URL.</p>
<p>#### Details
The WebUI error message renders `ExceptionMessage` (which can contain user-controlled input) as unencoded HTML. Server code that produces the message is in `common.py` - specifically `error_headers -&gt; _error_response -&gt; generate_http_error_flask`, which places `ExceptionMessage` into both response headers and the JSON body. The WebUI client then injects that text into the DOM using unsafe methods (examples in `lib/rucio/web/ui/static/*.js` such as `rule.js`, `request_rule.js`, `list_rules.js`) with `jQuery.html(...)` or equivalent, enabling reflected XSS when an attacker-controlled value is included in an error message (e.g. account, attribute, scope).</p>
<p>### PoC
1) Reflected XSS via account parameter (browse or load URL in WebUI context):
```text
https://127.0.0.1:8443/ui/account_rse_usage?account=%3Cimg%20src=x%20onerror=alert(document.cookie)%3E
```
Server response (excerpt):
```http
HTTP/1.1 500 INTERNAL SERVER ERROR
ExceptionClass: AccountNotFound
ExceptionMessage: Account &lt;img src=x onerror=alert(document.cookie)&gt; does not exist
Content-Type: application/octet-stream</p>
<p>{"ExceptionClass":"AccountNotFound","ExceptionMessage":"Account &lt;img src=x onerror=alert(document.cookie)&gt; does not exist"}
```</p>
<p>**XSS payload triggering…</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-h79m-5jjm-jm4q"/>
  </entry>
</feed>
