MISP Guard, a proxy enforcing security policies on MISP feed data, has a vulnerability where it incompletely validates required taxonomy tags. The guard verifies only that at least one tag from a required taxonomy is allowed but fails to ensure all tags from that taxonomy are allowed. This flaw allows events or attributes to carry both allowed and non-allowed tags simultaneously, bypassing data classification restrictions and potentially exposing sensitive data to unauthorized feed consumers. The issue affects event-level and attribute-level tag validation, including nested and shadow attributes. An attacker able to modify MISP events in a feed source can exploit this to leak higher-classification data through feeds intended for lower-classification data. The vulnerability has a CVSS 4.0 base score of 6.1 (medium severity). No patch or fix information is provided.
GitPython's Remote.pull() method improperly handles the positional refspec argument, allowing an attacker to inject a --upload-pack option that bypasses the unsafe-option guard. This leads to arbitrary command execution with the privileges of the calling process when using local-path or SSH transports. The vulnerability is fixed in version 3.2.0.
CVE-2026-99033 is a vulnerability related to the net/packet component, specifically concerning guarding the ll header push in the packet_rcv_spkt() function. The affected Microsoft product versions are 3.0 and 4.0. No CVSS score or detailed impact information is provided.
A flaw in Node.js HTTP Agent connection reuse can cause a client to accept as valid a response that was sent before the client has sent the request. This is an incomplete fix of CVE-2026-48931.
The guard that destroys idle keep-alive sockets when unexpected data arrives only runs when the event loop polls for I/O. If an unsolicited response has already reached the socket but has not been read yet when the socket is handed to a new request, for example because the event loop was busy with synchronous work, the guard is removed without seeing it and the data is parsed as the response to the new request.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.
The toml-node library version prior to 5.0.1 contains a prototype pollution vulnerability due to ambiguous key path encoding and insufficient ownership checks during TOML parsing. This allows a specially crafted TOML document to write properties onto Object.prototype, affecting all objects in the process. The vulnerability arises from a combination of ambiguous path rendering, guard clearing by table-array headers, and unchecked descent into objects such as Date instances. This can lead to widespread pollution of object prototypes, potentially enabling privilege escalation or denial of service.
GitPython versions from 3.1.30 up to but not including 3.2.0 contain a critical remote code execution vulnerability in the Remote.pull() method. The vulnerability arises because the unsafe-option guard only inspects keyword arguments and not positional refspec arguments, allowing attackers controlling the refspec to inject OS commands via the --upload-pack option. This can lead to execution of arbitrary commands as the calling process over local-path or SSH transports.
The insights-runtime-extractor runs as a privileged DaemonSet (`hostPID: true`)
that scans container processes for runtime fingerprinting. When scanning a
container, the coordinator:
1. **fork()s** a child process
2. **setns()** into the target container's PID and mount namespaces
3. **fchdir()** back to an orphaned FD pointing at the extractor's own root
filesystem (where `/crio.sock` is hostPath-mounted)
4. Calls **only `seteuid(target_uid)`** — changing the effective UID but leaving
the **real UID and saved-set-UID at 0** and **retaining the permitted
capability set**
5. The `check_no_privileged_perms()` guard inspects only the Effective capability
set (so it passes), and is **skipped entirely when the target runs as uid 0**
6. The `VersionExecutable` fingerprint invokes `fpr_kind_executable` with
`process.command_line[0]` — the target's argv[0], read from
`/proc/<pid>/cmdline` and **fully controlled by the workload**
7. `fpr_kind_executable` calls `exec.Command(executable, "--version").Output()`
— executing the **workload's own binary** inside the workload's mount
namespace while **ruid=0 in the host user namespace**
The executed process can call `setuid(0)` to restore full root with
`CAP_SYS_ADMIN`, and inherits the orphaned cwd which resolves into the extractor
container's filesystem containing the host CRI-O socket.
## Affected Code
### 1. Insufficient privilege drop (Rust — extractor coordinator)
**File:** `extractor/src/insights_runtime_extractor.rs`
```rust
// Lines 139-146 — seteuid-only drop, guard skipped for root containers
join_process_namespaces(process.pid)?;
change_dir(current_dir);
switch_user(*process.uid)?;
if *process.uid != 0 {
perms::check_no_privileged_perms()
.expect("Must not have privileged permissions to run fingerprints");
}
fingerprint::run_fingerprints(&config, out_dir, &process);
```
```rust
// Lines 182-185 — only effective UID changed; ruid/suid stay 0
fn switch_user(uid: u32) -> Result<(), ScannerError> {
debug!("... Becoming user: {uid}");
seteuid(uid.into()).map_err(|e| ScannerError::Errno(e))
}
```
### 2. Execution of untrusted binary (Go — fingerprint)
**File:** `fingerprints/pkg/utils/file.go`
```go
// Lines 75-80 — executes a path taken verbatim from workload's argv[0]
func GetExecutableVersionOutput(executable string) (string, error) {
out, err := exec.Command(executable, "--version").Output()
if err != nil {
return "", err
}
return string(out), nil
}
```
### 3. Workload-controlled path forwarded (Rust — version_executable)
**File:** `version_executable.rs`
```rust
// Lines 29-34 — workload-controlled command_line[0] forwarded to fingerprint
return Some(vec![
fpr_kind_executable,
out_dir.to_string(),
String::from(&process.command_line[0]),
String::from(&version_executable.runtime_kind_name),
]);
```
## Attack Pattern
**Attacker:** Any tenant able to schedule a pod (unprivileged, any namespace)
**Victim:** The node running the insights-runtime-extractor DaemonSet
**Trigger:** Automatic — the DaemonSet scans all container processes on the node
**Attack sequence:**
1. Attacker creates a pod whose process name matches a configured
versioned-executable pattern (`node`, `python`, `python3`, `MainThread`,
or contains `java`)
2. The pod's main binary (at the path matching argv[0]) is a malicious
executable that calls `setuid(0)` to restore root
3. When the insights operator triggers a scan, the DaemonSet forks, enters the
attacker's mount namespace, and executes the attacker's binary with ruid=0
4. The attacker's code regains full root with `CAP_SYS_ADMIN` in the host user
namespace
5. The inherited cwd contains the host CRI-O socket → full node compromise
The Salty documentation repository builds and deploys the docs.saltbox.dev website. Prior to commit 649c9aea2daef1168eeb0415b44e65dbbde9f220, .github/workflows/trigger-pr-build.yml records an untrusted fork commit in the pr_info artifact, and the secret-bearing workflow_run job in .github/workflows/build-pr.yml checks out that commit before running pip install -r requirements.txt. A fork pull request can therefore supply attacker-authored setup.py or PEP 517 build hooks whose installation code executes in the privileged base-repository workflow with CF_API_TOKEN, GH_TOKEN, MKDOCS_GIT_COMMITTERS_APIKEY, and a write-capable GITHUB_TOKEN, allowing secret disclosure and follow-on compromise. The vulnerability is not caused by the repository-fork guard, and the demonstrated path requires attacker control of fork content rather than merely the artifact metadata. This vulnerability is fixed with commit 649c9aea2daef1168eeb0415b44e65dbbde9f220.
FreeRDP versions from 3.9.0 up to but not including 3.32.0 contain an out-of-bounds read vulnerability in the RDPEAR NDR scalar readers. This flaw occurs because the code checks value length before consuming alignment padding, allowing malicious or compromised RDP servers to send crafted unaligned RDPEAR payloads. Such payloads, including CreateApReqAuthenticatorReq messages, can cause the client process to over-read memory and potentially crash. The vulnerability affects clients using Remote Credential Guard. The CVSS score is 5.3, indicating medium severity, with no confidentiality or integrity impact but a potential denial of service via client crash. No patch or remediation information is provided in the data. No known exploits in the wild have been reported.
wger contains an access control vulnerability affecting five gym management views where a gym-scope guard fails when both the requesting trainer and target user have no gym assigned (gym=None). This flaw allows an authenticated trainer with specific permissions and no gym assignment to access private admin notes, documents, contracts, user configurations, and permissions of any other unaffiliated user with gym=None. The root cause is a comparison that incorrectly allows access when both gym values are None, combined with querysets that lack secondary gym-scoped filtering.
CVE-2026-100689 is a path traversal vulnerability in GitPython 3.1.61 and main branch affecting the submodule update process. The vulnerability arises because the 'path' field from .gitmodules is used without proper containment validation, allowing an attacker to specify a path outside the repository directory. This can lead to directory creation and population outside the intended repository location. However, typical clone workflows are not affected because Git itself prevents checkout of .gitmodules entries with '..' components. Exploitation requires use of non-HEAD commits and custom submodule update calls. A fix is available in GitPython version 1.2.0.post0_16 that applies the existing containment guard to the 'path' field.
SiYuan Agent Tools versions up to 3.8.0 contain a Server-Side Request Forgery (SSRF) vulnerability due to a DNS rebinding time-of-check to time-of-use (TOCTOU) flaw. The vulnerability arises because the SSRF protection performs a single DNS resolution at guard time but does not verify the IP address at connection time, allowing an attacker-controlled domain to bypass the check by returning a public IP initially and a private or loopback IP on connection. This enables access to internal services such as cloud instance metadata. The issue affects the AI Agent tools' http_request and web_fetch components and was patched in version 3.8.1.
This update for jline3 fixes the following issue:
Update to upstream version 3.30.17:
* Security Fixes
+ Native Stack Buffer Overflow in Public INPUT_RECORD.memmove
JNI Method (Windows) (GHSA-6r3w-6jpj-x5w6)
+ Authenticated SSH Shell Channel Resource Leak via Null or
Non-Numeric PTY Dimensions (GHSA-7h86-pjwh-gpqj)
+ Authenticated SSH DoS via Unbounded Window-Change Terminal
Geometry (GHSA-m935-wqpj-pvp3)
+ TCP Socket File Descriptor Leak When Maximum Connections
Reached (GHSA-c87g-867h-cqr6)
* Bug Fixes
+ strip control characters from file names in posix builtins
+ bound !# history expansion to prevent exponential blowup
+ verify server host keys in the ssh client builtin
+ address remaining security vulnerabilities reported by
AFINE/CERT.PL
+ backport security fixes from master
+ backport security fixes to 3.x (path traversal + DSR plain
text)
+ strip control characters from ssh banner and prompts
* Dependency updates
+ bump com.diffplug.spotless:spotless-maven-plugin from 3.8.0 to
3.10.2
+ bump slf4j.version from 2.0.18 to 2.0.19
+ bump org.apache.maven.plugins:maven-surefire-plugin from 3.5.6
to 3.6.0
+ bump org.apache.maven.plugins:maven-compiler-plugin from
3.15.0 to 3.16.0
+ bump org.apache.felix:maven-bundle-plugin from 6.0.2 to 6.1.2
+ bump actions/setup-java from 5 to 6.0.0
+ bump org.graalvm.sdk:graal-sdk from 25.1.3 to 25.3.4.1
+ bump com.mycila:license-maven-plugin from 5.0.0 to 5.1.2
+ bump org.easymock:easymock from 5.6.0 to 5.7.0
+ bump com.google.jimfs:jimfs from 1.3.1 to 1.3.2
+ bump org.apache.maven.wrapper:maven-wrapper from 3.3.2 to
3.3.4
+ bump org.apache.maven:apache-maven from 4.0.0-rc-3 to
4.0.0-rc-6
+ bump eu.maveniverse.maven.njord:extension3 from 0.9.9 to
0.9.10
+ bump com.palantir.javaformat:palantir-java-format from 2.96.0
to 2.97.0
+ bump release-drafter/release-drafter from 7.6.0 to 7.7.0
+ bump groovy.version from 4.0.32 to 4.0.33
+ bump release-drafter/release-drafter from 7 to 7.6.0
+ bump org.apache.maven.plugins:maven-jar-plugin from 3.5.0 to
3.5.1
- Update to upstream version 3.30.16
* bugfix release with security hardening, SSH agent forwarding
fix, and terminal compatibility improvements.
* Breaking Changes
+ SSH agent forwarding is no longer enabled by default;
pass -A to explicitly request it
+ reject overlong hex components in OSC color responses
+ strip OSC and other escape sequences in ansiAppend
+ search multiple lib paths for versioned libutil.so
+ use Path.resolve instead of URI.resolve in cat and sort to
prevent SSRF
+ check closed flag in PtyInputStream to prevent hang on empty
input
+ confine ConfigurationPath lookups to the config directory
+ disable Read File command in nano restricted mode
+ drain buffered data before EOF in NonBlockingPumpInputStream
+ look up openpty in libc.so.6 for glibc 2.34+
+ guard styleMatches and highlighter rules against ReDoS
+ backport telnet DoS mitigations (GHSA-47qp, GHSA-2r2c)
+ propagate EOF in PtyInputStream to avoid infinite loop
+ bump org.apache.ivy:ivy from 2.5.3 to 2.6.0
+ bump actions/setup-node from 6 to 7
+ bump com.palantir.javaformat:palantir-java-format from 2.94.0
to 2.96.0
+ bump sshd.version from 2.18.0 to 2.19.0
+ bump org.codehaus.gmavenplus:gmavenplus-plugin from 5.0.0 to
5.1.0
+ bump org.graalvm.sdk:graal-sdk from 25.0.3 to 25.1.3
+ bump com.diffplug.spotless:spotless-maven-plugin
GitPython versions up to 1.2.0.post0_15 contain a vulnerability in the TagReference.create() method where a positional 'reference' argument can bypass the unsafe option guard for '--file'. This allows an attacker controlling the 'reference' parameter to cause an arbitrary local file read, with the file contents returned as the annotated tag message. The issue is an incomplete fix of a prior vulnerability and requires the embedding application to forward a user-controlled 'reference' value. A fix is available in version 1.2.0.post0_15.