<?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-11-22T14:03:44.923566+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/pysec-2025-19</id>
    <title>PYSEC-2025-19</title>
    <updated>2026-11-22T14:03:45.092803+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: picklescan</p>
<p>picklescan before 0.0.22 only considers standard pickle file extensions in the scope for its vulnerability scan. An attacker could craft a malicious model that uses Pickle and include a malicious pickle file with a non-standard file extension. Because the malicious pickle file inclusion is not considered as part of the scope of picklescan, the file would pass security checks and appear to be safe, when it could instead prove to be problematic.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2025-19"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/pysec-2024-115</id>
    <title>PYSEC-2024-115</title>
    <updated>2026-11-22T14:03:45.092913+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: langchain-community</p>
<p>A vulnerability in the GraphCypherQAChain class of langchain-ai/langchain-community version 0.2.5 allows for SQL injection through prompt injection. This vulnerability can lead to unauthorized data manipulation, data exfiltration, denial of service (DoS) by deleting all data, breaches in multi-tenant security environments, and data integrity issues. Attackers can create, update, or delete nodes and relationships without proper authorization, extract sensitive data, disrupt services, access data across different tenants, and compromise the integrity of the database.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/pysec-2024-115"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/debian-temp-0000000-277a82</id>
    <title>DEBIAN-TEMP-0000000-277A82 — TEMP-0000000-277A82</title>
    <updated>2026-11-22T14:03:45.092956+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Debian: weborf</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/debian-temp-0000000-277a82"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/debian-cve-2026-133422</id>
    <title>DEBIAN-CVE-2026-133422 — CVE-2026-133422</title>
    <updated>2026-11-22T14:03:45.093014+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Debian: pydantic</p>
<p>Validating an untrusted list into a field constrained with unique_items=True with Pydantic V1 takes quadratic time: an input of a few hundred kilobytes takes seconds to validate.  The ConstrainedList.unique_items_validator validator (in pydantic/types.py) checks each item against all the following ones. For a list with no duplicates (the common, valid case), this results in a quadratic number of comparisons.  The issue was fixed in commit 6ec75e57f277a820ec583e601167f25fe8dc7c87. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later.  Impact: denial of service through validation of untrusted input. Affected are applications validating untrusted lists into fields constrained with unique_items=True (using conlist() or Field()).  The fix only applies to lists of builtin scalar types (int, float, str, bytes, bool and None), for which duplicates can be detected in linear time. Lists of other types (e.g. models or dictionaries) are still checked in quadratic time, as their items aren't guaranteed to be hashable: bound their size using the max_items constraint.  Pydantic V2 models are not affected.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/debian-cve-2026-133422"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/debian-cve-2026-133276</id>
    <title>DEBIAN-CVE-2026-133276 — CVE-2026-133276</title>
    <updated>2026-11-22T14:03:45.093062+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Debian: pydantic</p>
<p>When extra data is allowed (extra=Extra.allow), providing a __pydantic_initialised__ key when validating a Pydantic V1 dataclass makes it considered as already validated, resulting in field values not being validated. The __init__() method of Pydantic V1 dataclasses stores all the provided keyword arguments in the instance __dict__ before validation, so a __pydantic_initialised__ keyword argument overrides the internal flag used to skip validation of already validated instances. As a result, data returned by validation doesn't match the declared type. Affected are applications validating untrusted data into Pydantic V1 dataclasses allowing extra data. The issue was fixed in Pydantic 1.10.27. Users relying on the pydantic.v1 namespace in Pydantic V2 should upgrade to 2.14.2 or later.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/debian-cve-2026-133276"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/debian-cve-2026-115642</id>
    <title>DEBIAN-CVE-2026-115642 — CVE-2026-115642</title>
    <updated>2026-11-22T14:03:45.093098+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Debian: python-keystonemiddleware</p>
<p>In OpenStack keystonemiddleware before 13.0.2, by supplying a custom X-Service-Token header in a request, anyone in possession of an access-restricted application credential may bypass those restrictions resulting in elevation of privileges.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/debian-cve-2026-115642"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:100634</id>
    <title>RHSA-2026:100634 — Red Hat Security Advisory: RHOAI 2.25.13 - Red Hat OpenShift AI</title>
    <updated>2026-11-22T14:03:45.093126+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>markdown: python-markdown: Denial of Service via inefficient inline link parsing bouncycastle: Bouncy Castle: Denial of Service via untrusted keystore length allocation org.bouncycastle/bcprov-jdk15on: org.bouncycastle/bcprov-jdk18on: org.bouncycastle/bc-fips: org.bouncycastle/bctls-fips: Bouncy Castle for Java: Denial of Service due to unbounded memory allocation fast-uri: fast-uri: Host confusion vulnerability via backslash in URI authority golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages google.golang.org/grpc/grpc-go: google.golang.org/grpc/authz: gRPC-Go: Authorization bypass due to improper HTTP/2 path validation crypto/x509: golang: Go crypto/x509: Certificate validation bypass due to incorrect DNS constraint application encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal tornado: Tornado: Cookie attribute injection due to improper handling of cookie arguments net/mail: golang: Go net/mail: Denial of Service via crafted email inputs golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Unauthorized command execution via discarded SSH permissions golang.org/x/crypto/ssh: golang.org/x/crypto/ssh: Denial of Service via resource leak from unsolicited SSH responses gola…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:100634"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:9848</id>
    <title>RHSA-2026:9848 — Red Hat Security Advisory: multicluster engine for Kubernetes v2.6.10 security update</title>
    <updated>2026-11-22T14:03:45.093395+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>lodash: prototype pollution in _.unset and _.omit functions golang: net/url: Memory exhaustion in query parameter parsing in net/url crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption rhacm: Open Cluster Management (OCM): Cross-cluster privilege escalation via improper Kubernetes client certificate renewal validation @remix-run/router: react-router: React Router vulnerable to XSS via Open Redirects axios: Axios affected by Denial of Service via __proto__ Key in mergeConfig immutable-js: Immutable.js: Arbitrary code execution via Prototype Pollution</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:9848"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:95612</id>
    <title>RHSA-2026:95612 — Red Hat Security Advisory: OpenShift Compliance Operator bug fix and enhancement update</title>
    <updated>2026-11-22T14:03:45.093429+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>golang: net/url: Memory exhaustion in query parameter parsing in net/url crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate net/url: Incorrect parsing of IPv6 host literals in net/url golang.org/x/net/html: golang: golang.org/x/net/html: Cross-Site Scripting via HTML parsing bypass crypto/x509: golang: golang crypto/x509: Denial of Service via excessive processing of DNS SAN entries crypto/x509: crypto/tls: golang: Go: Denial of Service vulnerability in certificate chain building crypto/tls: golang: Go crypto/tls: Denial of Service via multiple TLS 1.3 key update messages net: golang: Go net package: Denial of Service via long CNAME response in LookupCNAME net/http/internal/http2: golang: golang.org/x/net: Go HTTP/2: Denial of Service via malformed SETTINGS_MAX_FRAME_SIZE frame encoding/asn1: golang: Go encoding/asn1: Denial of Service via excessive recursion in Unmarshal net/mail: golang: Go net/mail: Denial of Service via crafted email inputs golang.org/x/net/idna: golang: net/http: golang.org/x/net/idna: Privilege escalation via incorrect Punycode label processing golang: Go os.Root: Symlink following vulnerability allows directory traversal net/mail: golang: net/mail: Denial of Service via pathological email address parsing mime: golang: Golang MIME: Denial of Service via maliciously-crafted MIME header net/http: golang: Go net/http: Unencrypted HTTP/2 connections vulnerable to Denial of Service html/template: golang: Go…</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:95612"/>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/rhsa-2026:9109</id>
    <title>RHSA-2026:9109 — Red Hat Security Advisory: containernetworking-plugins security update</title>
    <updated>2026-11-22T14:03:45.093481+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>golang: net/url: Memory exhaustion in query parameter parsing in net/url crypto/x509: golang: Denial of Service due to excessive resource consumption via crafted certificate crypto/tls: crypto/tls: Incorrect certificate validation during TLS session resumption net/url: Incorrect parsing of IPv6 host literals in net/url</p>
      </div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/rhsa-2026:9109"/>
  </entry>
</feed>
