<?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/bitnami_vulndb/10</id>
  <title>Most recent entries from bitnami_vulndb</title>
  <updated>2026-11-22T14:10:13.591743+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/bit-zookeeper-2026-115448</id>
    <title>BIT-zookeeper-2026-115448 — Apache ZooKeeper: Unbounded recursion in snapshot serialization allows a client to render the server unrecoverable</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: zookeeper</p>
<p>Uncontrolled recursion in Apache ZooKeeper. The server serializes its data tree to a snapshot by recursing one stack frame per znode level, with no depth bound. A client permitted to create znodes (the default root ACL is open) can build a chain of nested znodes deep enough that taking a snapshot exhausts the JVM stack and kills the snapshot thread; sizes stay within jute.maxbuffer, so existing limits do not prevent it. This is a denial of service that becomes persistent: on restart the server rebuilds the deep tree from its transaction log and fails again while taking the startup snapshot, so it does not return to service, and recovery can entail data loss. The same log affects a leader and its followers, so it can spread across an ensemble.</p>
<p>This issue affects Apache ZooKeeper 3.8.0 through 3.8.7 and 3.9.0 through 3.9.6. Users are recommended to upgrade to 3.8.8 or 3.9.7, which fix the issue. As a workaround, use ACLs and authentication to restrict znode creation rather than relying on the default open root ACL.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-115448"/>
    <published>2026-11-17T12:00:59.077000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100302</id>
    <title>BIT-zookeeper-2026-100302 — Apache ZooKeeper: Denial of service through unbounded memory allocation in multiRead request handling</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: zookeeper</p>
<p>Allocation of Resources Without Limits or Throttling in the multiRead request handler of Apache ZooKeeper allows a remote attacker to crash the server (denial of service) with a single small request.</p>
<p>The multiRead handler places no limit on the number of bundled read operations or on the cumulative size of the response it builds in memory. Because each operation's result is fully materialized and retained before serialization, a request that is small on the wire — within the jute.maxbuffer limit — but that references a large znode many times can force the server to allocate far more heap than the request size implies, exhausting the JVM heap and terminating the server with an OutOfMemoryError. Neither jute.maxbuffer nor largeRequestMaxBytes prevents this, as both bound only the inbound request, not the response.</p>
<p>This issue affects Apache ZooKeeper from 3.7.0 through 3.9.6. Users are recommended to upgrade to version 3.9.7, which enforces configurable limits on the multiRead operation count and cumulative response size.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100302"/>
    <published>2026-11-17T12:00:57.877000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100300</id>
    <title>BIT-zookeeper-2026-100300 — Apache ZooKeeper: Unauthenticated persistent denial of service via unvalidated quota-node data and paths crashing the t…</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: zookeeper</p>
<p>Improper handling of exceptional conditions in the quota subsystem of Apache ZooKeeper allows an attacker able to write under the /zookeeper/quota subtree — unauthenticated on default deployments, where that subtree is world-writable — to crash the server's critical request-processing thread and render the on-disk data directory permanently unbootable.</p>
<p>This issue affects Apache ZooKeeper up to and including 3.9.6. Users are recommended to upgrade to version 3.8.8 or 3.9.7, which fixes the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100300"/>
    <published>2026-11-17T12:00:56.688000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100252</id>
    <title>BIT-zookeeper-2026-100252 — Apache ZooKeeper: SASL authorization bypass on the client port through a client-supplied authorization ID</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: zookeeper</p>
<p>Improper Authorization vulnerability in Apache ZooKeeper.</p>
<p>When SASL authentication is enabled on the client port, the server's SASL callback handler grants every authorization identity (authzid) that a client requests, without checking it against the principal the client authenticated as. The server then tries to replace the requested identity with a canonical form of the authenticated principal, derived from the zookeeper.security.auth_to_local rules. If no rule applies to the principal, canonicalization fails and the error is only logged. The client-requested authzid then becomes the session's SASL identity for all ACL checks.</p>
<p>An authenticated client whose principal is not covered by the auth_to_local rules can therefore claim any SASL identity. With the default rules, this includes any Kerberos principal from a realm other than the server's default realm, such as a principal from a cross-realm trusted realm. The client then gets the permissions granted to that identity in sasl ACLs. If the requested identity matches a configured zookeeper.superUser, it gets superuser access to the whole data tree.</p>
<p>Users are recommended to upgrade to version 3.8.8 or 3.9.7, which fixes the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100252"/>
    <published>2026-11-17T12:00:55.506000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100235</id>
    <title>BIT-zookeeper-2026-100235 — Apache ZooKeeper: ACL enforcement bypass allows unauthorized operations to commit after an ACL revocation</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: zookeeper</p>
<p>Incorrect authorization due to a time-of-check to time-of-use (TOCTOU) race condition in the setACL request handling of Apache ZooKeeper.</p>
<p>When a node's ACL is changed via setACL, the pending change is not published to the server's outstanding change record for that node. Any request that is prepared (and authorized) after the setACL is submitted but before it commits is therefore checked against the previous, pre-revocation ACL, yet is applied to the data tree after the ACL change has taken effect. A client that currently holds a permission can use this window to perform operations requiring that permission through and after its revocation — for example, committing writes or deletes after losing write access, or re-granting itself full permissions, which persistently defeats the revocation. In deployments transitioning from the default OPEN_ACL_UNSAFE ACL to a restrictive ACL, any unauthenticated client can exploit this during the transition.</p>
<p>This issue affects Apache ZooKeeper up to and including 3.9.6. Users are recommended to upgrade to version 3.8.8 or 3.9.7, which fixes the issue.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-zookeeper-2026-100235"/>
    <published>2026-11-17T12:00:54.343000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-wordpress-2026-119977</id>
    <title>BIT-wordpress-2026-119977 — WordPress Core 4.7.0 - 7.1.3 - Unauthenticated Upgrade-Window Staged-Installer Remote Code Execution</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: wordpress</p>
<p>WordPress Core is vulnerable to Remote Code Execution in versions 4.7 through 7.1.3. This is due to predictable, web-accessible staging paths used during full-package core upgrades. This makes it possible for unauthenticated attackers to execute code on the server during the upgrade window.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-wordpress-2026-119977"/>
    <published>2026-11-17T12:02:15.170000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113723</id>
    <title>BIT-virtualenv-2026-113723 — virtualenv: Bash prompt values can change meaning under older compatibility modes</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: virtualenv</p>
<p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, caller-supplied prompt text can become executable syntax in the bash activation prompt. An attacker must influence the value passed to virtualenv, and a user must subsequently activate the environment and draw the prompt. This vulnerability is fixed in 21.14.9.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113723"/>
    <published>2026-10-29T09:00:39.883000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113720</id>
    <title>BIT-virtualenv-2026-113720 — virtualenv: Seeded files retain permissions from an older cache</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: virtualenv</p>
<p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, the app-data copy seeder uses shutil.copy() to copy cached package files into later environments, causing cached source modes to override the current run's umask. A cache populated under a permissive umask can therefore produce files writable by another local account in a later traversable environment, allowing package code such as pip/__init__.py to be modified and executed by the environment owner. The attacker cannot force the earlier umask, and a private destination parent prevents access. This issue is fixed in version 21.14.9.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113720"/>
    <published>2026-10-29T09:00:35.993000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113719</id>
    <title>BIT-virtualenv-2026-113719 — virtualenv: Seed replacement does not contain metadata deletion paths</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: virtualenv</p>
<p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, PipInstall._uninstall_previous_version() accepts existing seed-package metadata and _uninstall_dist() joins entries from top_level.txt and RECORD to site-packages without checking containment. When a reused destination contains distribution metadata influenced by another account, relative traversal, absolute entries, or linked parents can cause app-data reseeding to delete files outside the environment or the environment root with the invoking user's permissions, provided that user has deletion rights over the named paths. The deletion occurs during environment creation before any later use of the environment. Fresh environments without existing package metadata and creation with --clear do not enter this cleanup path. This issue is fixed in version 21.14.9.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113719"/>
    <published>2026-10-29T09:00:34.670000+00:00</published>
  </entry>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113718</id>
    <title>BIT-virtualenv-2026-113718 — virtualenv: Xonsh activation literals depend on the script decoding codec</title>
    <updated>2026-11-17T12:14:43.364000+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Bitnami: virtualenv</p>
<p>virtualenv is a tool for creating isolated virtual python environments. Prior to 21.14.9, POSIX xonsh activation quote() uses repr() to write printable non-ASCII prompt or destination data into UTF-8 activate.xsh, while xonsh can read that script using $XONSH_ENCODING. Under a legacy multibyte codec such as GBK or Big5, a UTF-8 trail byte can consume the backslash before an adjacent quote, allowing the literal to close and attacker-influenced statements to execute when the user sources the generated script. This issue is fixed in version 21.14.9.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/bit-virtualenv-2026-113718"/>
    <published>2026-10-29T09:00:33.381000+00:00</published>
  </entry>
</feed>
