<?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:43:19.065444+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/ghsa-4vrc-j85c-598c</id>
    <title>GHSA-4vrc-j85c-598c — Spring Security Doesn't Correctly Include Servlet Path in Path Matching of XML Authorization Rules</title>
    <updated>2026-09-30T00:43:19.085239+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Maven: org.springframework.security:spring-security-config</p>
<p>Vulnerability in Spring Spring Security. If an application uses &lt;sec:intercept-url servlet-path="/servlet-path" pattern="/endpoint/**"/&gt; to define the servlet path for computing a path matcher, then the servlet path is not included and the related authorization rules are not exercised. This can lead to an authorization bypass. This issue affects Spring Security: from 7.0.0 through 7.0.4.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/ghsa-4vrc-j85c-598c"/>
  </entry>
</feed>
