Curated security, hosting and development news with vulnerability warnings from fixed trusted sources.
CISA KEVGHSACERT.atHosting
Updated
About these news
Articles are collected periodically from a fixed source list. D4rC Tools stores the headline, source summary and source link only; linked articles are not fetched on page view.
gosaml2: Unauthenticated panic decrypting an EncryptedAssertion with a short or empty CipherValue
·GitHub Advisories
### Summary An attacker who can supply a crafted SAML Response for parsing can crash a gosaml2 service provider by sending an EncryptedAssertion with AES-GCM encryption metadata and a CipherValue shorter than the GCM nonce size (12 bytes). The library panics with slice bounds out of range before any validation completes. This is a **distinct issue from [GHSA-hwqm-qvj9-4jr2](https://github.com/russellhaering/gosaml2/security/advisories/GHSA-hwqm-qvj9-4jr2)**, which addressed panics in the AES-CBC decryption path (commit [3418f9ae09063ff8df0ce1bd93f24e538e614def](https://github.com/russellhaering/gosaml2/commit/3418f9ae09063ff8df0ce1bd93f24e538e614def), included in v0.10.0). That fix added a block-size check for CBC but left the AES-GCM path completely unprotected. ### Details `…
### Impact An unauthenticated request can occupy one synchronous application worker for seconds. Concurrent requests add CPU cost and can keep all workers busy, sustaining denial of service without user interaction. ### Patches The issue has been patched in versions 9.0.967 and 9.1.968-beta. ### Workarounds Disallow the style attribute.
Doorkeeper: When using public clients, any client can revoke any access token
·GitHub Advisories
### Summary An improper authorization issue affects Doorkeeper's OAuth token revocation flow when public (non-confidential) clients are in use. This vulnerability can lead to tokens being revoked without correct authorization. The issue is fixed in Doorkeeper 5.9.1.
OmniFaces: SSE push channels are not bound to their owning HTTP session
·GitHub Advisories
## Summary [GHSA-fp43-vj7g-pg92](https://github.com/omnifaces/omnifaces/security/advisories/GHSA-fp43-vj7g-pg92) (fixed 5.4.2) bound session- and view-scoped **WebSocket** (o:socket) push channels to the HTTP session that registered them, so a leaked channel ID can no longer be connected to from a foreign or absent HTTP session. The fix ([d5cae243c4](https://github.com/omnifaces/omnifaces/commit/d5cae243c4692555efaa4ba774e0f8f60e3f4db5)) touched only the Socket* classes. The parallel **SSE** (o:sse, added in 5.2) push transport was left unchanged. SseEndpoint.doGet accepts a connection whenever the presented channel ID is in the application-wide registry, without ever checking that the caller's HTTP session owns it. A leaked session/view-scoped SSE channel ID can therefore be re…
October: Media Library Crop Handler Bypasses Upload Extension Allowlist
·GitHub Advisories
The Media Library upload handler validates the destination filename against an extension allowlist (default_extensions), rejecting types such as php, phtml, html, and htm. The image crop handler (MediaManager::onCropImage / cropImage) did not perform this check. The destination filename was taken from user input, the extension was extracted from it, and the staged bytes were written to the public media folder under that attacker-chosen extension. Combined with the fact that upload accepts any file contents under an allowlisted extension (a PHP payload disguised as .jpg), and that the zero-dimension crop branch performs a byte-for-byte File::copy rather than re-encoding the pixels, an authenticated backend user with the media.library.create permission could write a file…
Servo Sandbox bypass: declarative refresh can auto-navigate a sandboxed iframe
·GitHub Advisories
A sandboxed iframe can auto-navigate itself via declarative refresh even when automatic features should be blocked. This allows attacker-controlled embedded content to redirect itself without user action. ### Summary Servo allows a sandboxed iframe to auto-navigate itself via declarative refresh in configurations that should block automatic features. The issue reproduces in the must-block rows of the matrix: - sandbox="" - sandbox="allow-same-origin" - sandbox="allow-forms" - sandbox="allow-same-origin allow-forms" This is a client-side sandbox-policy bypass. It does not by itself prove script execution or parent DOM access, but it does let attacker-controlled sandboxed content redirect itself without user action. ### Details The declarative refresh path is missing sandbox enforce…
XWiki Platform: HQL injection in search allows unauthenticated database extraction including password hashes
·GitHub Advisories
### Impact The query REST API allows executing HQL queries to filter the listed pages. While this properly checks access rights for the current user, the query can be used to combine when clauses and blind queries, to recover values, through FROM clause injection to join BaseObject and StringProperty tables, bypassing the HQL validator's SELECT column whitelist. This allows recovering any data that is stored in the database, including data from inaccessible pages, password hashes and passwords stored in configuration properties. For a typical password hash, this requires about 800 requests to the REST API (about one per bit). It should be assumed that when using more complex techniques, this even works when the attacker cannot read any wiki page. Password hashes use salted SHA1 in XWiki w…
SharpIppNext: Unbounded IPP Document Stream Buffering Leads to Denial of Service
·GitHub Advisories
### Summary SharpIppNext's IppProtocol.ReadIppRequestAsync() unconditionally copies the entire attacker-supplied IPP document payload into an unbounded MemoryStream with no size limit. Because this behavior is enabled by default (ReadDocumentStream = true) and the official server documentation shows HttpContext.Request.Body being passed directly to ReceiveRequestAsync() without authentication, an unauthenticated remote attacker can exhaust the server process's memory by sending an arbitrarily large IPP request body, causing an Out-Of-Memory (OOM) condition and denial of service. > [!NOTE] > This vulnerability only affects server-side implementations (using SharpIppServer to parse incoming IPP requests). It does not affect client-side implementations using SharpIppClient or c…
obsidian-sync-mcp: Missing Host/Origin validation lets a public website drive a victim's Obsidian vault via DNS rebinding (no-auth mode)
·GitHub Advisories
When obsidian-sync-mcp runs without MCP_AUTH_TOKEN (the documented no-auth mode for local use), the HTTP MCP endpoint does not validate the Host or Origin header before dispatching MCP methods (CWE-350). The no-auth mode's "local network only" assumption therefore does not hold: a malicious web page the operator visits can use DNS rebinding to resolve an attacker-controlled hostname to 127.0.0.1 (or the operator's LAN/VPN/Docker-published address) and issue requests the server accepts as trusted local calls, reaching the full tool surface (read_note, write_note, edit_note, delete_note, move_note, list_notes, list_folders, list_tags, get_note_metadata). Affected versions:
Tapir: Construction/decode RCE via property name -> raw case-class field (tapir-openapi-codegen)
·GitHub Advisories
The OpenAPI code generator (tapir-openapi-codegen-core) builds Scala source by string templating and emitted several names/values from the (untrusted) OpenAPI document without escaping or validation, allowing injection of arbitrary Scala that runs at generated-code compile time and/or endpoint-assembly time (build/codegen-time RCE from an attacker-controlled spec). This advisory covers the full class of sinks, all sharing one root cause and one fix (PR #5395, commit e015939b7): object property names (-> case-class fields), query/header/path parameter names (-> endpoint input DSL), and operation tags (-> .tags(List(...))). The fix routes identifier-position names through validation/quoting and string-literal values through JavaEscape.escapeString. Consolidates the separately-reported query…
Todoist MCP Server: Browser DNS rebinding lets websites write and delete Todoist data through local MCP server
·GitHub Advisories
The self-hosted todoist-mcp-http server accepts browser-origin MCP requests with attacker-controlled Host and Origin headers. A malicious website can use DNS rebinding to route its own origin to a victim's local 127.0.0.1 MCP server, then invoke Todoist MCP tools without a caller credential. This affects github.com/Doist/todoist-mcp at commit d2903e0d945d2a559d71c091337ad6380511e62f, package version 10.3.1, when the optional Streamable HTTP server is running. The stdio entrypoint is not browser-reachable. The vulnerable browser-reachable component is todoist-mcp-http. The documented HTTP server mode runs all MCP tools with the operator's TODOIST_API_KEY and binds to loopback by default: ``bash TODOIST_API_KEY=your-key npx -p @doist/todoist-mcp todoist-mcp-http `` `src/…
### Summary Gortex is an MCP server exposing write_file, edit_file, and move_inline tools. resolveFilePath **exempts absolute paths** from confinement, and the write handlers — unlike read_file / get_symbol_source — **never call guardSymlinkWithinRepo**. A single MCP write_file call with an absolute path writes any file the daemon user can, **outside every indexed repo root** (AtomicWriteFile's MkdirAll auto-creates missing parents). Writing ~/.zshrc, ~/.bashrc, .git/hooks/pre-commit, or a cron/systemd unit yields code execution on the next shell/commit. This directly violates the project's own SECURITY.md invariant *"File-path resolution is **confined to indexed repository roots**"* ### Affected internal/mcp/tools_fileops.go (+ tools_move_inline.go), HEAD…
OpenID4VP: X.509 chain validation accepts a forged certificate that reuses a trusted anchor's Subject DN without verifying its signature
·GitHub Advisories
## Summary ChainBuilder (the private RFC 5280 validator behind TrustEvaluator and the public credential-parsing API) terminated chain building on **Subject Distinguished Name string equality** rather than on cryptographic closure to a trust anchor. A certificate whose Subject DN string matched a trusted anchor's Subject DN was accepted as the chain terminus **with no signature verification** against the anchor's public key. An attacker who mints a self-signed certificate and copies a trusted anchor's Subject DN string onto it can therefore have that certificate — and any credential signed with its private key — accepted as issued under a trusted authority. ## Impact A relying party using @openeudi/openid4vp to verify OpenID4VP presentations (mdoc / SD-JWT VC) could be induced to acc…
keystore-go: Keystore integrity and password verification bypass via stripped trailing digest in Decode()
·GitHub Advisories
### Summary keystore.Decode() fails to check the error returned when reading the trailing SHA-1 integrity digest of a JKS keystore. If an attacker removes the final 20 bytes from a .jks file, the digest read returns an empty slice and the byte-comparison loop never executes, so Decode() returns the parsed keystore with err == nil. This defeats both tamper detection and — for certificate-only truststores — the password check itself, allowing an attacker with write access to a keystore file (but without knowledge of the keystore password) to silently inject or replace trusted CA certificates. ### Details **Affected versions:** github.com/pavel-v-chernykh/keystore-go ≤ v2.1.0+incompatible (the final release on this module path). v3 and v4 releases are not impacted. In `decoder.go…
Axon: Download of Code Without Integrity Check in axon-mcp
·GitHub Advisories
### Summary axon rtk-install downloads a pre-built rtkx binary from GitHub releases and executes it via subprocess.run() on every text-compression call, without verifying its integrity — no checksum, signature, or attestation check anywhere in the download/install path. If the release pipeline or a maintainer token for sammyjdev/rtkx were ever compromised, every axon user who installs or auto-bootstraps rtkx would silently download and execute an unverified binary with the same privileges as the axon process. ### Details The download path lives in src/axon/context/rtk_bootstrap.py: - _http_download() fetches the release archive over HTTPS via urllib.request.urlopen() and writes the raw response bytes to disk — no hash comparison against any published value. - _extract_binary() unpacks the…
The easiest way to fool someone is to give them something they already expect. A job offer. A message about a service outage. A familiar app. Nothing looks strange at first. And that's the problem. This week's stories show how ordinary things are being used to steal data, spread malware, and get people to hand over access. There's another shift worth watching. AI is making some attacks easier
phpAfterShell Explained: How Hackers Could Turn a PHP Session Flaw Into Code Execution
·The Hacker News
PHP's default file-based session storage can be made to return objects an attacker chose, by cutting off a session write at the right moment. When combined with a second weakness, such as a suitable gadget chain in the app, those objects can allow the attacker to run code on the server. Today's PHP releases fix the flaw, called phpAfterShell. The flaw is tracked as CVE-2026-126714 and rated
Jane: Instantiation RCE via query parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
·GitHub Advisories
### Summary jane-php (open-api-3) builds PHP via nikic/php-parser (AST), so string literals are escaped -- but PHPDoc comment text is emitted RAW. The generated Client/Endpoint method docblocks embed the query parameter name verbatim in a @param array{ ""?: ... } block. A */ in the query name closes the /** ... */ docblock early and lands in class-body position; because the name is a raw string key (not identifier-mangled), the */ and following PHP survive. Injecting */ public function __construct(){ } /* adds an attacker-controlled __construct to the generated Client class, which runs when the client is instantiated -> RCE (CWE-94). Verified 7.11.2/PHP8.1. ### Impact Generating a client from an attacker-influenced OpenAPI document and using the generated SDK (instantiating the…
Jane: Instantiation RCE via header parameter name -> raw PHPDoc */ breakout (jane-php/open-api-3)
·GitHub Advisories
### Summary jane-php (open-api-3) builds PHP via nikic/php-parser (AST), so string literals are escaped -- but PHPDoc comment text is emitted RAW. The generated Client/Endpoint method docblocks embed the header parameter name verbatim in a @param array{ ""?: ... } block. A */ in the header name closes the /** ... */ docblock early and lands in class-body position; because the name is a raw string key (not identifier-mangled), the */ and following PHP survive. Injecting */ public function __construct(){ } /* adds an attacker-controlled __construct to the generated Client class, which runs when the client is instantiated -> RCE (CWE-94). Verified 7.11.2/PHP8.1. ### Impact Generating a client from an attacker-influenced OpenAPI document and using the generated SDK (instantiating th…
Jane: Instantiation RCE via parameter description -> raw PHPDoc */ breakout (jane-php/open-api-3)
·GitHub Advisories
### Summary jane-php (open-api-3) builds PHP via nikic/php-parser (AST), so string literals are escaped -- but PHPDoc comment text is emitted RAW. The generated Client/Endpoint method docblocks embed the parameter description verbatim in a @param array{ ""?: ... } block. A */ in the parameter description closes the /** ... */ docblock early and lands in class-body position; because the name is a raw string key (not identifier-mangled), the */ and following PHP survive. Injecting */ public function __construct(){ } /* adds an attacker-controlled __construct to the generated Client class, which runs when the client is instantiated -> RCE (CWE-94). Verified 7.11.2/PHP8.1. ### Impact Generating a client from an attacker-influenced OpenAPI document and using the generated SDK (instan…
DOMShell: domshell_eval classified as read-tier can execute side-effecting JavaScript without --allow-write
·GitHub Advisories
### Summary The domshell_eval MCP tool (and the eval command inside domshell_execute) was classified as **read-tier**, allowing it to run without the --allow-write server flag. However, eval and the write-tier js command dispatch to the same handler in the extension and call CDP Runtime.evaluate with the raw expression string and no side-effect gate. Any JavaScript expression could therefore mutate DOM, window, or global state through domshell_eval without the operator's --allow-write authorization. The tool description explicitly promised "(read-only) ... always available in read-only mode" — the misclassification contradicted the documented contract, not just an implicit one. ### Impact No new capability was exposed — the same write access was already available via `do…
djangocms-moderation: Moderation comments disclosed to non-participant staff via the admin changelist
·GitHub Advisories
## Summary The Django admin views for moderation comments (CollectionCommentAdmin and RequestCommentAdmin) render the full comment body but scope access only by an attacker-controlled id in the URL and Django's model-level view_*comment permission. They perform no per-object participant check. As a result, any authenticated staff user who holds the comment *view* permission can read the comments of **any** collection or moderation request — including ones they are not a participant of — simply by supplying the target object's id. Comments are documented and intended to be private to the participants of a collection (its author and the moderators assigned to its workflow). This advisory concerns a read/write authorization asymmetry: the write paths already enforced `request.user ==…
Mareforma: Unsigned Claims Can Be Promoted to REPLICATED via Missing Signature Enforcement in Convergence Path
·GitHub Advisories
### Summary mareforma 0.3.3 contains a critical integrity flaw in the REPLICATED convergence logic (_maybe_update_replicated_unlocked() in mareforma/db/core.py:1300-1319). The peer-selection SQL query that determines whether two independent claims "agree" on the same anchor does not verify that either claim carries a valid cryptographic signature from an enrolled validator key. Because rekor_enabled=False is the default and automatically sets transparency_logged=1 at insert time, every claim — signed or not — immediately satisfies the convergence precondition. An attacker with no Mareforma key can write an unsigned claim to a shared graph, cause it to converge with a legitimate signed peer claim, and have it promoted to REPLICATED status. The forged REPLICATED row is then re…
Mareforma: transparency_logged trusts the unsigned rekor block
·GitHub Advisories
## What's wrong During restore, transparency_logged is recomputed as 1 if (toml_logged is not False and bundle_has_rekor) else 0, where bundle_has_rekor comes only from a rekor.uuid field inside signature_bundle. That derivation is wrong in both directions. First, the rekor block is metadata attached after signing (attach_rekor_entry in mareforma/signing/rekor.py leaves the payload and signatures untouched), so it is not covered by the Ed25519 signature. A hand-edited claims.toml can add "rekor": {"uuid": "x"} to any claim's bundle and forge the "publicly witnessed by Rekor" state. The claim signature still verifies, and restore never cross-checks the block against [rekor_inclusions] or the log. Tampering with claims.toml is the exact threat model restore defends aga…
Mareforma: invalidated claims still promote to REPLICATED
·GitHub Advisories
## What's wrong _maybe_update_replicated_unlocked never checks t_invalid, so a claim that a signed contradiction verdict has marked invalid can still climb to REPLICATED through convergence detection, and it pulls an honest peer up with it. Three gaps line up: - The new-claim short-circuit reads only status and asserter_keyid (core.py:1339-1352); an invalidated but still-open new claim passes. - The candidate-peer SELECT filters status = 'open', unresolved = 0, and transparency_logged = 1 but has no t_invalid predicate (core.py:1390-1410), so an invalidated existing claim qualifies as a convergence partner. - The promotion UPDATE gates only on status = 'open' (core.py:1422-1426), leaving a TOCTOU window even after the SELECT is fixed. A signed contradiction verdi…
Mareforma: verify_bundle never checks a per-claim signature
·GitHub Advisories
## What's wrong verify_bundle documents that it verifies "a bundle's DSSE envelope AND each per-claim signature", lists "per-claim signature failure" among its raised errors, and promises that partial verification never surfaces "an authenticated bundle that contains some invalid claims" as success. The code does not do this. The JSON-LD predicate built by JSONLDExporter._claim_node carries no signature material (there is no signatureBundle field on the node), so the verify loop has nothing cryptographic to check per claim. It only re-derives each claim's canonical-statement digest from the node fields and compares it to the signed subject list: ```python chain_input = _signing.canonical_statement({...node fields...}, node.get("evidence") or {}) expected = hashlib.sha256(chain_input…
## What's wrong search_claims never calls _row_verified_on_read. Its row loop applies only the PRELIMINARY-unenrolled filter, then appends the row. query_claims runs the same projection but additionally re-verifies REPLICATED/ESTABLISHED signatures on read (line 4023) and drops any row that fails, per the documented tamper guarantee in the comment block above it: a high-trust row whose signature does not verify is excluded from query results entirely. So a tampered or forged high-trust row splits the two read paths. Any process with DB write access, or an attacker copying a genuine validation envelope onto a fresh row, can flip a row to ESTABLISHED. query() drops it; search() serves it at its persisted trust level. Verified in a runtime check against a forged ESTABLISHED row: ``…
### Background NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT and edge computing. The NATS Server MQTT support uses internal $MQTT.* subjects to implement MQTT protocol features such as QoS handling. ### Problem Description An authenticated MQTT client could subscribe to an internal MQTT delivery subject that was not intended to be available to clients. This bypassed configured subscribe permissions for that internal subject family and exposed MQTT QoS2 protocol metadata for sessions in the account. Message payloads were not exposed through this path. This issue was related to an incomplete restriction on internal MQTT subjects. It affected MQTT users whose ordinary subscribe permissions would not otherwise al…
### Background NATS.io is a high performance open source pub-sub distributed communication technology, built for the cloud, on-premise, IoT and edge computing. The NATS Server supports MQTT clients and can bridge MQTT activity into NATS subjects across routes and leafnode connections. ### Problem Description An MQTT client could include protocol control characters in subscription filters that were later forwarded as NATS protocol data to route or leafnode connections. This could corrupt the forwarded protocol stream and allow injection of unintended NATS protocol operations, potentially across cluster nodes or accounts where route or gateway connections are present. Anonymous MQTT deployments are higher risk because no credentials are required to reach the affected parser. Authenticated d…
Kritische Sicherheitslücken in PHP - Updates verfügbar
·CERT.at
19. November 2026 Beschreibung Das PHP-Projekt hat am 19. November 2026 Sicherheitsupdates veröffentlicht, die unter anderem sieben als kritisch eingestufte Sicherheitslücken beheben. Die Schwachstellen betreffen die Session-Verwaltung (ext-session), die Datums-Erweiterung (ext-date), PHP-FPM sowie die Zend Engine und können unter bestimmten Konfigurationsvoraussetzungen zur Ausführung von beliebigem Code führen. CVE-Nummer(n): CVE-2026-115560, CVE-2026-126714, CVE-2026-129182, CVE-2026-129289, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496 CVSS v4.0 Base Score: jeweils 9.2 (kritisch) Auswirkungen Bei erfolgreicher Ausnutzung können Angreifer:innen beliebigen Code mit den Rechten des PHP-Worker-Prozesses ausführen. Zudem sind Speicherkorruption, Abstürze von Worker-Prozessen (Denial-of…
A critical flaw in VMware vCenter lets an attacker with network access bypass authentication and gain unauthorized access to the system, Broadcom, which owns VMware, said in an advisory published today. Fixed versions are out for all supported branches, and the company lists no workaround. vCenter is the central console for managing an organization's ESX hosts and virtual machines. The
PHP Fixes 7 Critical Flaws, Including Bugs That Could Allow Remote Code Execution
·The Hacker News
The PHP Foundation has released security updates to address multiple critical security flaws that could be exploited to achieve remote code execution on affected deployments, including CVE-2026-115560. The list of vulnerabilities is as follows - CVE-2026-115560 (CVSS score: 9.2) - An improper input validation vulnerability that could result in remote code execution, file modification,
Drupal Patches Critical Installer Flaw That Could Give Unauthenticated Attackers Control of Sites
·The Hacker News
Under specific conditions, a critical vulnerability in Drupal core can allow an attacker without login credentials to use the built-in installer to attempt to reinstall a site. That can lead to a site takeover or remote code execution, and the project rates the vulnerable configurations as uncommon. Fixed releases for all supported branches shipped yesterday. The Drupal Security Team disclosed
Internet traffic and attacks during the 2026 U.S. midterm elections
·Cloudflare
On November 3, 2026 U.S. voters headed to the polls. Here’s what Cloudflare data across more than 1,400 protected sites tells us about Election Day Internet traffic and cyberattacks.
Everything Is a Web Application, Including Your Firewall
·The Hacker News
One of the early targets of PHP2Shell exploitation was the firewall. On October 28, Palo Alto Networks confirmed that attackers were exploiting the two PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, against PAN-OS management interfaces exposed to the internet. Both flaws let anyone execute code on the web server without authentication. The disclosure itself went a little wrong.
Hackers Breach N-able Cloud Server, Disrupting Email Security Management Across 3 Regions
·The Hacker News
N-able on Wednesday disclosed that unknown threat actors gained unauthorized access to one of the servers in the Mail Assure and Spam Experts Hosted Cloud, causing it to disable management interfaces and APIs. "We have taken steps to mitigate the threat and are continuing to harden our services to reduce the risk of recurrence," N-able said. "The investigation is ongoing, but at this time we
Ruby Releases Fixes for 7 Regex and String Flaws, Warns 5 Have Proof-of-Concept RCE
·The Hacker News
Ruby contains seven memory-safety flaws in its regular expression engine and its string case-conversion code. For five of them, its maintainers say, proof-of-concept exploits, or PoCs, have shown that crafted input can run code on the machine. "We are aware of PoCs that prove some of them can be used to trigger remote code execution," the maintainers said. The project released fixed versions
Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle
·The Hacker News
Low-privilege database accounts that cannot read a single application table can still be used to run code on the database server itself, a researcher has shown, by reaching memory-corruption bugs in the engine code behind ordinary SQL. The exploits, published yesterday, are the researcher's proofs of concept against PostgreSQL, MySQL and ClickHouse, plus a separate Oracle chain that needs no
CISA Warns of 4 Exploited Flaws Linked to Ransomware, Cryptomining, and LLMjacking Attacks
·The Hacker News
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Wednesday added four vulnerabilities impacting Synology DiskStation Manager (DSM), BerriAI LiteLLM, Apache Axis, and Vanderbilt University Research Electronic Data Capture (REDCap) to its Known Exploited Vulnerabilities (KEV) catalog, citing evidence of active exploitation. The vulnerabilities are listed below -
PHP Warns of Critical Security Flaws Affecting All Supported Versions, Fixes Coming November 19
·The Hacker News
The maintainers of the PHP programming language on Wednesday issued an advisory announcing an upcoming security release that addresses critical flaws. The release is scheduled for November 19, 2026, between 2 and 2:30 p.m. UTC. "These releases are part of PHP's regular four-week release cycle and will address security vulnerabilities affecting all supported PHP versions," the maintainers said.
PGPainless: Unbounded Compressed Packet Descent in inline-detach and MessageInspector leads to Denial of Service (DoS)
·GitHub Advisories
### Summary An architectural security boundary bypass in inline-detach and MessageInspector allows remote, unauthenticated attackers to force unbounded recursive decompression routines. By supplying a specially crafted OpenPGP message containing deeply nested compressed packet structures, an attacker can completely bypass the library's built-in DoS protections (MAX_LAYER_DEPTH = 16), leading to resource exhaustion, thread blocking, and potential Out-of-Memory (OOM) application crashes. ### Details The pg-painless core processing pipeline implements a defensive threshold constraint to prevent decompression bomb sequences (Zip Bombs) and arbitrary resource consumption: Enforcement Location: pgpainless-main/pgpainless-core/src/main/kotlin/org/pgpainless/decryption_verification/MessageMetadat…
cassandra-jdbc-wrapper: Authentication Token Exposed in Logs
·GitHub Advisories
### Summary The fix for [AIKIDO-2024-10565](https://intel.aikido.dev/cve/AIKIDO-2024-10565) (plaintext password logging) introduced two redaction helpers — DriverUtil.toStringWithoutSensitiveValues() and DriverUtil.redactSensitiveValuesInJdbcUrl() — but both helpers only redact the "password" property/parameter (JdbcUrlUtil.TAG_PASSWORD). The equally sensitive "token" property (JdbcUrlUtil.TAG_TOKEN), used for DataStax Astra and other token-based Cassandra authentication, is completely unredacted by both helpers. Applications using token-based authentication with DEBUG logging enabled will therefore log the live authentication token in plaintext via SessionHolder's calls to these same two helpers — the exact same exposure pattern that the original fix was intended to prevent…
mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses
·GitHub Advisories
Several tools in mssql-mcp-core built T-SQL by string-interpolating caller-supplied identifiers and predicates directly into the statement passed to the node-mssql Request.query() batch API. Only data values were parameterized. Affected tools and inputs: - update_data, delete_data: tableName and the free-form whereClause were interpolated raw. - insert_data: tableName and column names (object keys) were interpolated raw. - execute_transaction: the same raw tableName/whereClause interpolation per operation. - create_table, create_index, drop_table: table/column/index/schema identifiers were interpolated with no or insufficient validation. - list_databases (reader tier): the stateFilter argument was interpolated raw into the query, with only a non-enforced in…
Miren Runtime: Authentication bypass in RPC layer: unverified TLS client certificates grant cluster superuser access
·GitHub Advisories
### Summary The Miren Runtime RPC server (QUIC/HTTP3, default port :8443) requested TLS client certificates but never verified that a presented certificate chained to the cluster Certificate Authority. Because a client-certificate identity is granted a blanket RBAC bypass, any party able to reach the RPC listener could present a forged, self-signed certificate and be authenticated as a cluster **superuser** — no valid CA signature, credential, or prior authorization required. ### Impact This is a complete, unauthenticated authentication bypass against the cluster control plane. An attacker who can reach the RPC port can perform any RPC operation with full privileges: enumerate and manipulate entities, apps, sandboxes, disks, and other cluster resources. This yields full compromise of co…
An updated Clairic and Clairic-flash are now open-weight, from the new Workers AI Superintelligence team
·Cloudflare
Add your teaser here. It should complement the headline, not repeat it. Teaser cannot be longer than 240 characters. The Blog Review Gem will suggest an excerpt. Clairic graduates from preview, while Clairic-flash joins the repertoire on Workers AI. We’re doing an open-weight release for both extraction models.
OliveTin: Second-Order OS Command Injection via shellAfterCompleted
·GitHub Advisories
## Summary OliveTin's shellAfterCompleted post-execution hook injects unsanitized variables — including arbitrary command output (output), the authenticated username (ot_username), and the exit code (exitCode) — directly into a shell command template processed by sh -c. Unlike the main action's argument handling, **no checkShellArgumentSafety validation is applied** to these variables. An attacker who can influence the output of a command (e.g., via user-supplied arguments that reflect in stdout, or through trusted-header username spoofing) can inject arbitrary OS commands into the post-execution shell. This is a **distinct** finding from CVE-2026-27626 (OS command injection via password type in webhooks). That CVE addressed argument types bypassing shell safety checks in th…
django-filer: Missing per-object authorization on `discard` and `edit_redirect` version transitions
·GitHub Advisories
## Summary When django-filer's optional per-folder permission system is enabled (FILER_ENABLE_PERMISSIONS=True), the "Delete files and/or folders" admin action does **not** enforce per-folder edit permissions the way every other mutating action does. A staff user who is scoped **read-only** on a folder via FolderPermission (can_edit = DENY), but who holds the global Django model-level delete_* permission, can delete files and entire subfolders inside that folder — even though their move, rename, copy, and resize actions on the same folder are correctly denied. This is an integrity / edit-control gap (unauthorized deletion). It is **not** a read-confidentiality issue: filer files are world-downloadable by design, so no confidentiality claim is made. ## Affected versions - django-fi…
djangocms-versioning: Authorization Bypass Through User-Controlled Key and Missing Authorization
·GitHub Advisories
## Summary The discard and edit_redirect version transitions did not enforce a per-object change-permission check, while the sibling transitions (archive, publish, unpublish, revert) all did. As a result a low-privileged staff user could **discard (delete) any draft version — and thereby the underlying content object — of content they have no change permission on**, and could create an editable draft off any published version, by supplying a version primary key they should not have access to (an insecure direct object reference). ## Details Version state transitions are guarded by Conditions objects declared on djangocms_versioning.models.Version. Every transition that mutates content carries the user_can_change condition, which delegates to the *content* object's own pe…
LLMKube: Arbitrary Host File Read via Model.spec.source hostPath Injection
·GitHub Advisories
### Summary LLMKube's ModelReconciler accepts arbitrary absolute paths and file:// URIs in the Model.spec.source field and propagates them to two distinct sinks without path allowlisting: (1) os.Open() inside the controller pod itself (copyLocalModel), and (2) a Kubernetes HostPathVolumeSource that mounts the attacker-supplied path into the inference pod's init container. Any namespace user with permission to create or update Model and InferenceService custom resources can read arbitrary files accessible to the controller pod (e.g., the controller's own Kubernetes service-account token) or arbitrary files on the node where the inference pod is scheduled (e.g., /etc/kubernetes/kubelet.conf). Model caching, the feature that activates the hostPath sink, is **enabled by de…
install-artifact-from-github loads downloaded native artifacts without integrity verification
·GitHub Advisories
## Description bin/install-from-cache.js downloads a prebuilt native addon (*.node) over the network and writes it directly to the artifact path **with no cryptographic integrity verification of any kind** — no checksum manifest, no signature, no SRI. A scan of the whole package for createHash|sha256|checksum|integrity|digest|signature finds nothing. The file is then require()-loaded by the consumer, which executes the addon's native module-init code. Anyone able to influence the download achieves code execution on the installing machine. ### Affected code (v1.6.0) - **Mirror is fully attacker-steerable via an env var, no host pinning** — bin/install-from-cache.js:80: ``js let assetUrl = mirrorHost || process.env[mirrorEnvVar] || 'https://github.com'; `` re2 passes `--host-v…
Chainguard SDK: AWS SigV4 token replay in auth/aws.VerifyToken — Chainguard-Audience/Chainguard-Identity binding headers not required in SignedHeaders
·GitHub Advisories
### Summary The auth/aws package of the chainguard.dev/sdk Go library provides Chainguard's AWS-backed identity federation (an AWS workload proves its identity to Chainguard by signing an AWS STS GetCallerIdentity request). Its verifier, VerifyToken, reads the Chainguard-Audience and Chainguard-Identity binding headers from a presented token but does not require them to be covered by the SigV4 signature. AWS STS validates only the headers listed in SignedHeaders and ignores all others, so an attacker can take a GetCallerIdentity request that a victim signed for a *different* relying party, inject or rewrite those two headers *after* signing (without invalidating the signature), and replay it to any service that authenticates callers with VerifyToken. The binding those he…
ALTCHA PHP: verifySolution bypasses HMAC signature check when challenge signature is absent
·GitHub Advisories
In altcha-org/altcha v2, the verifySolution method skips HMAC signature verification when the signature field is absent from the challenge payload, even when hmacSignatureSecret is configured. An attacker who strips the signature key from the challenge JSON passes the condition as false, bypassing tamper-detection entirely. The PoW solution check then runs against unverified parameters — allowing an attacker to self-issue a low-difficulty challenge, solve it trivially, and submit a payload that verifies as true. Impact: Complete CAPTCHA bypass on any deployment that sets hmacSignatureSecret (the recommended production configuration). Fix: The check was split so that a missing signature is explicitly rejected when a secret is configured.
Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins
·GitHub Advisories
### Impact Outstatic’s authenticated GitHub REST proxy accepted an unvalidated endpoint parameter and constructed an upstream GitHub API URL by string concatenation while attaching the authenticated user’s GitHub OAuth token. A user with access to the Outstatic dashboard could craft a request that caused the server to send their own GitHub OAuth token to a non-GitHub host. If that token was captured, it could be used to access GitHub resources available to that same user, including private repositories depending on granted scopes. This does not allow unauthenticated attackers to access private repository data, and it does not directly expose another user’s GitHub token without an additional same-origin execution or request-forging primitive. ### Patches The issue has been patched by valid…
Atomic Server: Unauthenticated full-response SSRF in Atomic-Server /bookmark endpoint
·GitHub Advisories
## Summary Atomic-Server exposes a GET /bookmark endpoint that fetches an attacker-supplied URL server-side, parses the response, and reflects the fetched content back to the caller. The endpoint requires no authentication and performs no authorization of its own, and the underlying fetch helper applies no allow-list or private-IP deny-list. An unauthenticated attacker with network reach to the server can force it to issue arbitrary outbound HTTP GET requests to internal-only hosts (loopback services, internal admin panels, link-local cloud-metadata) and read the response body back. This is a full-response SSRF, not a blind one. ## Root cause (source trace) 1. The bookmark endpoint is registered unconditionally for every server: server/src/appstate.rs:69 (`store.add_endpoint(plugins::…
Atomic Server: Unauthenticated `/setup` invite grants write access to the entire Drive
·GitHub Advisories
## Summary atomic-server provisions a well-known invite at {server}/setup with write = true, target = the Drive root, and usagesLeft = 1. Invite redemption **ignores the redeemer's identity** (for_agent: _ in server/src/plugins/invite.rs:22), so possession of the URL is the only requirement. An **unauthenticated** attacker who sends GET /setup?public-key= has the server create a new Agent and grant it **write access to the entire Drive**. On a freshly deployed (not-yet-claimed) instance this is a full server takeover with no credentials. ## Severity **Critical — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (9.8).** No authentication required; grants attacker-controlled write over all resources in the Drive. ## Affected component - server/src/appstate.rs — creates the `/set…
Atomic Server: Arbitrary file read via user-controlled `internalId` in the `/download` handler (leaks root agent private key)
·GitHub Advisories
## Summary The Commit apply path enforces **no allowlist of writable properties**, so any authenticated Agent can set the internalId string (datatype string, no character validation) on a resource it owns. The /download handler then uses that value **verbatim** as a filesystem path — file_path.push(internal_id); NamedFile::open(file_path) — with **no sanitization and no containment check** (server/src/handlers/download.rs:56-65). By setting internalId to a traversal path (../../../../etc/passwd) or an absolute path (PathBuf::push of an absolute path replaces the buffer), an attacker reads **any file on the host**. The highest-value target is the server config file storing the **root agent private key**, which yields full server compromise. Only the *upload* path sanitizes…
Atomic Server: Stored XSS via uploaded files served inline (same-origin) on `/download` → account takeover
·GitHub Advisories
## Summary Files uploaded via POST /upload are served back by GET /download/{path} using actix_files::NamedFile. For text/html and image/svg+xml, actix-files (0.6.6) sets Content-Disposition: inline, so the browser **renders** the file instead of downloading it. The /download route sets **no Content-Security-Policy, no X-Content-Type-Options: nosniff, and no forced attachment** (CSP exists only on the SPA route), and files are served from the **same origin** as the app UI. An authenticated Agent uploads evil.html containing ``; when a victim opens the link, the script executes in the app origin. Because the atomic_session cookie is set via document.cookie (not HttpOnly) and the Agent's Ed25519 private key is stored in same-origin IndexedDB (`browser/data-browser/…
A flaw in NGINX's HTTP/2 support can allow an attacker to run code on servers with HTTP/2 enabled, without needing to log in. The decade-old flaw, CVE-2026-123007, dubbed "nginx2root," has been present in NGINX's open-source code since version 1.9.5, released on September 22, 2015. Fixed versions 1.31.9 and 1.30.7 came out today. F5, the company behind NGINX, says attackers can run code where
F5 Warns 6 Critical BIG-IP Flaws Can Crash Traffic in Specific Setups, May Allow RCE
·The Hacker News
Six critical vulnerabilities in F5 BIG-IP allow an attacker to crash the Traffic Management Microkernel (TMM) without logging in, disrupting traffic until the TMM restarts. Each flaw needs a specific setup on a virtual server: an iRule that uses a particular command, or an APM policy that includes two particular kinds of agent. F5, which makes BIG-IP, disclosed the flaws today and says they
Critical Apache Roller RCE Flaw Under Active Exploitation, No Authentication Required
·The Hacker News
A critical security flaw in Apache Roller, an open-source, Java-based blogging platform, has come under active exploitation in the wild, according to the Apache Software Foundation (ASF) The vulnerability, tracked as CVE-2026-129448 (CVSS score: 9.8), is a case of unauthenticated deserialization in the XML-RPC endpoint that could lead to remote code execution. "Deserialization of Untrusted
Mustache for Ruby: RCE using built-in method access
·GitHub Advisories
> [!NOTE] > The vulnerability was fully disclosed to the maintainer in private prior to security advisories were enabled for the project. > This advisory presents a limited information for initial release to provide a time window for installing updates. Full information with PoCs would be added later. ## Summary Mustache template engine for Ruby in versions 1.1.2 and earlier allows remote attackers to achieve arbitrary code execution through accessing specific built-in methods in an attacker-supplied template. ## Details Mustache is often suggested as a safe simple template language to avoid SSTI vulnerabilities.[^1] [^2] Mustache for Ruby up to version 1.1.2 did not properly restrict method access which allowed chaining multiple built-in methods to achieve arbitrary code execution. > [!I…
augment-virShell allows Command Injection in `grep()` via Unsanitized `searchPattern`
·GitHub Advisories
## Shell Command Injection in grep() via Unsanitized searchPattern ### Summary The grep() function exported by @augment-vir/node inserts caller-controlled search patterns directly into a double-quoted shell command string without sanitization (grep.ts:310). When the constructed command is passed to spawn() with shell: 'bash' (shell.ts:98-99), bash evaluates $() command substitution expressions embedded in the pattern, resulting in arbitrary OS command execution as the Node.js process user. Any downstream application that passes untrusted input to grep()'s pattern or patterns field is vulnerable to unauthenticated local (and potentially remote) code execution. CVSS Base Score: **7.8 (High)**. ### Details **Root cause:** packages/node/src/augments/fs/grep.ts:310 ma…
### Summary KZG accumulator public-instance limbs were decoded without consistently enforcing canonical limb bounds before reconstructing elliptic-curve coordinates. In the generated EVM verifier, accumulator coordinates were reconstructed from public-instance limbs using shifted additions before point validation. The verifier checked the reconstructed point, but did not independently check that every limb was below the configured limb bound before reconstruction. ### Details PlonkProof::read takes accumulator public-instance scalars selected by accumulator_indices and passes them into AccumulatorEncoding::from_repr. For the EVM loader, LimbsEncoding::from_repr forwards those limbs to EvmLoader::ec_point_from_limbs, where each coordinate was reconstructed with shl and add be…
Kritische Sicherheitslücken in NGINX Plus und NGINX Open Source - Updates verfügbar
·CERT.at
18. November 2026 Beschreibung In NGINX Plus und NGINX Open Source existieren mehrere Sicherheitslücken in den Modulen ngx_http_v2_module (HTTP/2), ngx_http_v3_module (HTTP/3) und ngx_mail_proxy_module (Mail-Proxy). Es handelt sich um Use-after-free-Schwachstellen sowie einen Heap-Buffer-Overflow, deren Ausnutzung zum Absturz von Worker-Prozessen und unter bestimmten Voraussetzungen zur Ausführung von beliebigem Code führen kann. F5 bewertet die Schwachstellen nach CVSS v4.0 als kritisch. CVE-Nummer(n): CVE-2026-123007, CVE-2026-121810, CVE-2026-123633, CVE-2026-113425 CVSS Base Score: jeweils 8.1 (CVSS v3.1) bzw. 9.2 (CVSS v4.0) Auswirkungen Durch Ausnutzen der Schwachstellen können Angreifer:innen aus der Ferne NGINX-Worker-Prozesse zum Absturz bringen (Denial-of-Service) oder deren Spe…
How Cloudflare WAF helps protect against Java4Shell (CVE-2026-114938)
·Cloudflare
Java4Shell is a critical memory-corruption flaw in OpenJDK's Base64 decoder that can lead to remote code execution. Cloudflare has released six WAF managed rules for paid plans that logs matching requests by default. Patch your Java runtimes now.
New EggStreme Malware Variant Goes Silent to Evade Security Tools in Government Attacks
·The Hacker News
The suspected Chinese advanced persistent threat (APT) group behind the sophisticated EggStreme malware has rebuilt its toolkit as it continues to target government organizations in the Philippines. "When attackers are exposed, the cheap response is to rotate," Bitdefender said in a technical report shared with The Hacker News. "A file hash changes with every recompile, a domain costs a few
Kritische Sicherheitslücke in Java (Java4Shell) - Updates verfügbar - CVE-2026-114938
·CERT.at
18.11 2026 Beschreibung In Java existiert eine kritische Sicherheitslücke, die es nicht authentifizierten Angreifer:innen ermöglicht, Schadcode aus der Ferne auszuführen. Betroffen sind Programme die Java 17.0.6 oder später verwenden, beispielsweise Keycloak, Atlassian Jira, Atlassian Confluence, JFrog Artifactory, Jenkins, und PingFederate. Mit einem authentifizierten User konnte Remote Code Execution auf Plattformen wie Apache Kafka Broker, Apache Solr, Elasticsearch, Gerrit, und Spinnaker erzielt werden. Schadcode kann ausschließlich auf x86-64 Intel und AMD Prozessoren welche das AVX-512 VBMI Instruktionsset unterstützen. Die Memory Corruption kann durch 64 Zeichen in Kombination mit einem `` =` ausgelöst werden (respektive 128 Zeichen für ältere OpenJDK Versionen), und im schlimmsten…
New Attack Bypasses TPM Lockout to Crack Windows Hello and BitLocker PINs in Days, Not Years
·The Hacker News
On AMD-based PCs and some Intel PCs, the TPM lockout for Windows Hello and BitLocker PINs can be reset by someone who opens the PC's case, researchers at Technische Universität Berlin say. That leaves short PINs open to guessing. In lab tests, the researchers found a four-digit Hello PIN on an AMD laptop and a 6-digit BitLocker PIN on an Intel laptop this way. Both PINs were set by the
AI Pentesting Checklist for Web Apps: 15 Questions to Ask Before Choosing a Vendor
·The Hacker News
TL;DR Attackers move first. On average, exploitation now starts before a patch exists (Mandiant M-Trends 2026). In 1H 2026, 23% of vulnerabilities VulnCheck added to its exploited list were hit on or before disclosure day. AI pentesting vendors aren't interchangeable. Most look convincing in a demo. The gaps show up in your logged-in flows, your coverage, and your production safety. Make
Quality Isn’t The Main Worry About AI Pentesting — Data Privacy and Production Safety Are
·The Hacker News
AI is speeding up how software is built, which means more code, more changes, and more chances for vulnerabilities to reach production. It's speeding up how attackers find and exploit them too, with time-to-exploit now down to a single day. Security testing has to keep up with both. AI pentesting has emerged as a way to run in-depth tests whenever teams need them, instead of waiting for the
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Tuesday added a critical security flaw impacting Perforce Puppet, an enterprise infrastructure-as-code (IaC) and configuration management platform, to its Known Exploited Vulnerabilities (KEV) catalog, citing reports of active exploitation. The vulnerability, tracked as CVE-2026-115731 (CVSS score: 9.4), is a case of
CISA Urges Immediate Patching of Java4Shell Flaw That Could Allow Remote Code Execution
·The Hacker News
The U.S. Cybersecurity and Infrastructure Security Agency (CISA) has urged organizations to immediately patch a newly disclosed critical security flaw impacting Oracle Java. The flaw, tracked as CVE-2026-114938 (CVSS score: 8.1), refers to a case of out-of-bounds write that can lead to denial-of-service (DoS) or remote code execution under certain conditions. "This critical memory-corruption
Threat actors have compromised Microsoft's agent-framework package to push a credential stealer, according to reports from Aikido, Endor Labs, OX Security, SafeDep, Socket, StepSecurity, and Google-owned Wiz. The malicious versions, 1.26.1 and 1.26.2, were published 33 minutes apart on November 17, 2026, and are designed to run a credential stealer on every Python start. As of writing, both the
Russian COLD RELIC Hackers Use Stolen Google Workspace Data to Breach Second U.S. Organization
·The Hacker News
The Russia-linked cyber espionage group known as Cold Relic (formerly COLDRIVER and UNC4057) has been observed weaponizing a single cloud compromise into a launchpad for a series of linked intrusions resulting in third-party compromise. Google's Mandiant and Threat Intelligence Group (GTIG) said it investigated a 2026 compromise at a U.S.-based organization in which the adversary leveraged
Java4Shell (CVE-2026-114938) Enables Pre-Auth RCE in Jira, Jenkins, Keycloak on Java 17+ AVX-512 VBMI Servers
·The Hacker News
A Java flaw called Java4Shell can let attackers without an account run their own code on Jira, Jenkins, Keycloak, and three other widely used applications, says Calif, the security research firm that disclosed it this week. The flaw is present in Java 17.0.6 and later, and the vulnerable code runs only on x86-64 Intel and AMD chips that support the AVX-512 VBMI feature. Tracked as
Synology DiskStation Manager (DSM): Synology DiskStation Manager (DSM) Improper Encoding or Escaping of Output Vulnerability
·CISA KEV
Synology DSM contains an improper encoding or escaping of output vulnerability in the system plugin daemon in Synology BeeStation OS (BSM) that could allow a remote attacker to execute arbitrary code via unspecified vectors.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
BerriAI LiteLLM contains an unprotected alternate channel vulnerability that could allow remote attackers to execute arbitrary code via bytecode rewriting at the /guardrails/test_custom_code URI.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Vanderbilt University Research Electronic Data Capture (REDCap): Vanderbilt University Research Electronic Data Capture (REDCap) Code Injection Vulnerability
·CISA KEV
Vanderbilt University Research Electronic Data Capture (REDCap) contains a code injection vulnerability which could allow an unauthenticated attacker to execute arbitrary code on the server. An attacker could exploit this via crafted HTTP requests that access an unintended controller route from a public survey context and supply a crafted file-path or stream parameter during data import processing. Exploitation requires knowledge of a valid public survey hash.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
Apache Axis contains an unsafe reflection vulnerability that could allow an unauthenticated remote attacker to execute arbitrary code via a crafted SOAP fault message that causes Axis to load and instantiate an attacker-specified class when a suitable class is available on the application classpath. The impacted product(s) could be end-of-life (EoL) and/or end-of-service (EoS). Users are advised to discontinue use and/or transition to a supported version.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
libp2p: gossipsub creates a permanent topics-map entry per distinct subscription with no cap in the default config
·GitHub Advisories
### Summary A single gossipsub peer can grow a node's topics map without bound by flooding subscription RPCs, because the default configuration has no global, per-peer, or topic-length cap and peer scoring does not penalise subscription volume. The peer is never greylisted, so the growth continues toward OOM. ### Details handleReceivedSubscription (packages/gossipsub/src/gossipsub.ts:1028, line 1036) runs this.topics.set(topic, new Set()) for every distinct topic string: ``ts private handleReceivedSubscription (from, topic, subscribe) { let topicSet = this.topics.get(topic) if (subscribe) { if (topicSet == null) { topicSet = new Set() this.topics.set(topic, topicSet) // no global cap, no per-peer cap } topicSet.add(from.toString()) } } `` The only topical gate (`gossipsub.ts:981…
libp2p: ASN.1 DER decoder drives an unbounded synchronous loop on attacker-controlled length fields, stalling the Node event loop pre-auth
·GitHub Advisories
### Summary A remote peer can stall a js-libp2p node's entire event loop for ~4–5 seconds per connection (and transiently allocate ~2 GB) by sending a ~15-byte crafted publicKey inside an Identify message. The malformed key reaches the DER decoder before any peer-id/signature check, so the attack is pre-auth and repeatable indefinitely by reconnecting. ### Details packages/crypto/src/keys/rsa/der.tsreadLength() parses DER long-form lengths with no comparison to buf.byteLength, and readInteger() then loops over the attacker-claimed length: ```ts function readInteger (buf, context) { const length = readLength(buf, context) // attacker-controlled, claims up to 2^64 const end = context.offset + length for (let i = context.offset; i < end; i++) // runs far past buf.byteLength vals.p…
SAML2: Incomplete fix of CVE-2026-49283: unsigned embedded Response bypasses HTTP-Artifact signature verification (no embedded-Issuer binding)
·GitHub Advisories
## Summary CVE-2026-49283 / GHSA-6929-8p9f-26jx ("HTTP-Artifact TLS validator confusion allows cross-IdP authentication bypass") was fixed so that HTTPArtifact::receive() verifies the embedded SAML Response using the IdP metadata signing keys. The current implementation (master 31c72c1d, released **v6.2.3**) reaches that verification **only when the embedded Response is signed**: ``php // src/Binding/HTTPArtifact.php (receive()) if (!$samlResponse->isSigned()) { return $samlResponse; // ← unsigned embedded Response returned UNVERIFIED } return $this->verifyMessageSignature($samlResponse, $idpMetadata); // only runs when signed `` An attacker who controls one trusted-federation IdP therefore returns a **validly-signed outer ArtifactResponse** (signed with their own real key, whic…
Filament Curator: Stored XSS via unsanitized SVG upload served inline
·GitHub Advisories
## Summary SVG files uploaded through the Curator media panel are stored and served inline without any sanitization. An authenticated user with permission to upload media can upload an SVG containing embedded JavaScript. When another panel user opens that file via the **View** action (which opens the media as a top-level browser document), the embedded script executes in the origin of the Filament application. image/svg+xml is included in the default accepted MIME types, so a default installation is affected unless SVG uploads have been explicitly disabled. ## Impact Because the SVG is served as a **top-level document** (not embedded in an `` tag), any ``, event-handler attribute (e.g. onload), or javascript: URI inside it runs with full script privileges in the application's origin…
Filament Curator: Cross-tenant media metadata disclosure via Curator picker search
·GitHub Advisories
Summary In multitenant Filament panels, an authenticated user could retrieve media metadata belonging to other tenants by typing in the Curator media-picker search box. The search query omitted the tenant ownership scope that the normal file listing applies. Details CuratorPanel::updatedSearch() built its Eloquent query independently of getFiles() and did not apply the filament()->hasTenancy() && $isTenantAware tenant-ownership where clause. As a result, the search matched media across all tenants. A secondary flaw compounded it: the orWhere('title'…) chain was not wrapped in a nested group, so the OR conditions also broke out of the isLimitedToDirectory constraint. The issue was introduced in v3.2.4, when multitenancy support was added to the media picker. Impact - Who: any authenticated…
qbee-agent: Local Privilege Escalation and Arbitrary File Tampering via Symlink Following in createFile helper
·GitHub Advisories
This is a Local Privilege Escalation (LPE) vulnerability stemming from improper symlink handling (CWE-59: Link Following) and improper ownership management (CWE-282) inside the qbee-agent file manager logic. ### Impact Any managed device running qbee-agent up to the affected versions. The impact manifests in three distinct vectors: 1. **Primary Vector (Full Privilege Escalation to Root - Default Configuration)**: If an unprivileged user's account is managed by the SSH Keys bundle, they can replace or remove their own ~/.ssh directory and create a symlink pointing to /root/.ssh. On the next configuration apply, qbee-agent follows the symlink and writes the user's server-provisioned public key directly into /root/.ssh/authorized_keys. Since the symlink resides inside the user's own ho…
EGroupware: User-Controlled Identity Provider Selection in SAML Authentication
·GitHub Advisories
### Summary The login() function at line 130 passes the raw user-supplied value $_REQUEST['idp'] directly to SimpleSAMLphp's requireAuth() with only a regex check that the string starts with 'https://'. No validation is performed against a list of configured, trusted IdP entity IDs. An unauthenticated attacker can supply any HTTPS URL pointing to an IdP they control. ### PoC ``php //api/src/Auth/Saml.php function login() { // login (redirects to IdP) $as = new SimpleSAML\Auth\Simple(self::$auth_source); $as->requireAuth(preg_match('|^https://|', $_REQUEST['idp']) ? ['saml:idp' => $_REQUEST['idp']] : []); `` ### Impact An attacker can redirect authentication to a malicious IdP to capture credentials via phishing, or, if the SimpleSAMLphp configuration does not strictly validate IdP m…
AWS-advanced-jdbc-wrapper: Java Deserialization RCE via Cache Poisoning
·GitHub Advisories
### Impact The AWS Advanced JDBC Wrapper is an open-source JDBC driver wrapper that extends a JDBC driver to enable Amazon Aurora and AWS Cloud features such as failover handling and caching. We identified CVE-2026-14265, an issue in the RemoteQueryCachePlugin of the AWS Advanced JDBC Wrapper. When this plugin is enabled, query results read from the shared Redis/Valkey cache are deserialized without class filtering. An actor with write access to the shared cache infrastructure could insert a crafted serialized Java object that, when read by an application, results in execution of arbitrary code on the application server. ### Workarounds The RemoteQueryCachePlugin is not enabled by default. Customers who cannot immediately upgrade can mitigate this issue by disabling the RemoteQueryCachePl…
Quad9’s withdrawal from France: A canary in the coal mine
·Cloudflare
Quad9's forced withdrawal from France highlights the dangers of mandating DNS-level blocking. We explore why forcing public resolvers to act as content filters is technically flawed and threatens the open Internet.
pympp allows excessive sponsored transaction fees through padded calldata
·GitHub Advisories
### Details When the server acts as the fee_payer, pympp 0.8.0 validates calldata using eth_abi decoding, which is lenient about trailing bytes. The FeePayerPolicy caps gas_limit (≤ 2 M) and max_fee_per_gas (≤ 100 Gwei) but does **not** check calldata length. Tempo uses legacy calldata gas pricing: **16 gas per non-zero byte**. Appending N bytes of 0x01 padding inflates actual gas used by N × 16 while keeping gas_limit and max_fee_per_gas within policy caps. The server cosigns and broadcasts the padded transaction, draining its fee-payer wallet. **Vulnerable code path:** FeePayerPolicy in fee_payer_policy.py (pympp 0.8.0) enforces maxGas = 2_000_000 and maxFeePerGas = 100 Gwei but has no calldata.length bound. The policy check passes because the inflated gas…
Phoenix: Format String Injection in applyChatTemplate
·GitHub Advisories
- Summary A format string injection vulnerability in the applyChatTemplate GraphQL endpoint allows an attacker to read server-side environment variables, cryptographic secrets, and internal module attributes directly from the API response. On default Phoenix installations where authentication is disabled the endpoint is reachable with no credentials. On auth-enabled deployments, any account regardless of privilege level is sufficient to exploit it. - Impact Server filesystem paths, loaded Python module names, and internal configuration constants are fully disclosed, an attacker with network access can read the full server os.environ including the admin credentials hardcoded in phoenix.auth. Successful exploitation allows an attacker to extract PHOENIX_SECRET, the master key used to si…
Researchers Claim Two RCE Exploits That Bypass Telegram’s New Android Defenses
·The Hacker News
A malicious widget can bypass the security filter that Telegram added to its Android app last week and run code outside it, according to NebuSec, a security company. Widgets are small interactive blocks that bots send inside chat messages, and their JavaScript runs on the user's phone. The researchers ran their demonstration on a Telegram test server, because only approved bots can send
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
·GitHub Advisories
With Cache Components enabled, an outer 'use cache' function can be keyed incorrectly even when its inner 'use cache' call generates a fresh entry. If the inner function reads a root param (via next/root-params) and returns a value that still contains pending promises — for example an object with data that is ready immediately alongside slower data — React Flight delivers the ready portion to the outer function before the inner entry has finished publishing its root param dependencies. The outer function can then finish, and its cache entry is persisted under a key that omits that root param. The entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value. Entries written this way can also ignore…
Oracle to Patch 11 Java Flaws Today as Critical OpenJDK RCE (CVE-2026-114938) Report Emerges
·The Hacker News
Oracle is preparing to release security patches for 11 vulnerabilities in Java SE on Tuesday, November 17, 2026, all of which may be exploited remotely without authentication, as separate reports warn of a potentially critical remote code execution (RCE) flaw affecting OpenJDK. The 11 vulnerabilities carry a maximum CVSS 3.1 severity score of 8.1, according to Oracle's advance security notice.
Trigram Campaign Impersonates About 50 AI and Blockchain Brands to Target Devs with Infostealers
·The Hacker News
Artificial intelligence (AI), blockchain, and logistics sectors across Europe and the U.S. have emerged as the target of a large-scale, industrialized campaign dubbed Trigram. "Trigram is a large-scale campaign that impersonates about 50 brands in the blockchain and AI sectors, to trick developers into executing an infostealer themselves," Stormshield said in a deep-dive technical report
Hackers Found a Way Around GitHub SHA Pinning. This Webinar Explains How to Close the Gap
·The Hacker News
Pinning GitHub Actions to an exact version of their code, known as SHA pinning, has become the go-to defense against software supply chain attacks. Attackers have already found a way around it. In March 2026, the hackers who hijacked Trivy, a widely used open-source security scanner, planted malicious code that looked like it came from GitHub's official checkout tool. They even labeled it a
Researchers Detail iPhone Flaw That Let Apps Record Audio Despite Denied Microphone Permission
·The Hacker News
A now-patched flaw in Apple's audio service let apps on iPhones and iPads record audio even after the user tapped "Don't Allow" on the microphone prompt. The first security updates with the fix came out on August 17. Neither Apple nor the two researchers who found the flaw report that it was used in attacks. Nik Tsytsarkin of Meta Red Team X published the technical details last week. Mustafa
New GitDoor and GraphDoor Backdoors Turn GitHub and SharePoint Into Covert C2 Channels
·The Hacker News
Government sectors in Asia and Africa have been targeted by an active cyber intrusion campaign that delivers to previously undocumented backdoors that leverage legitimate services like Microsoft SharePoint and GitHub for command‑and‑control (C2). The activity has been codenamed Operation ShadowCloud by Kaspersky. The Russian cybersecurity company said it identified the campaign in early 2026.
Apple Tightens macOS App Permissions to Limit Data Access Amid AI Agent Security Risks
·The Hacker News
Apple on Monday introduced new controls that allow Mac users to give more granular access to data they give to apps, including those that use artificial intelligence (AI) agents. The changes, currently previewed in macOS 27.3 beta 2, relate to increased transparency and more options for two of its APIs: Device Control and Data Access, and Full Disk Access. "Before granting an app such
Hijacked Optimizely Scripts Served Card Skimmer and iOS Exploit Kits to CNN, BBC and Zoom Visitors
·The Hacker News
An attacker exploited a flaw in Optimizely Web Experimentation to plant malicious code in some of the scripts that customers' websites load from the service, Optimizely said early today. Visitors to sites run by at least 178 organizations, including CNN, the BBC and Zoom, received the code yesterday, according to Report URI, a firm that monitors the scripts websites run. The code was built to
ConnectWise Warns ScreenConnect Attacks Continue as SCKit Targets Unpatched Systems
·The Hacker News
ConnectWise on Monday said it completed its investigation into unauthorized access targeting partner ScreenConnect environments, and recommended customers to ensure that the technician client is running version 26.6.5 or later. The company said additional activity targeting on-premises environments continues to be reported where the identified third-party extensions remain enabled, and
N-able Patches 17 N-central Flaws as Attackers Exploit Earlier Bugs to Deploy Crypto Miners
·The Hacker News
N-able has released a new security update to address additional critical security flaws impacting N-central. Describing N-central 2026.4 Hotfix 3 as a critical security update, the company said it includes a number of security patches and fixes that enhance the security of the Remote Monitoring and Management (RMM) and Unified Endpoint Management (UEM) platform. "HF3 builds on the
Perforce Puppet Enterprise: Perforce Puppet Enterprise Deserialization of Untrusted Data Vulnerability
·CISA KEV
Perforce Puppet Enterprise contains a deserialization of untrusted data vulnerability in Puppet’s report-processing code that allows a client with any CA-signed agent certificate to execute arbitrary code on the Puppet Server as the service user by submitting a report containing a crafted rich-data type through a PUT request. If the certificate authority automatically signs requests without strong verification, an unauthenticated network attacker can obtain a valid certificate and exploit the vulnerability.
Required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
## Summary qbee-agent contains a Zip Slip vulnerability in app/utils/tar.go. The tar extractor checks whether an entry remains inside the destination directory with: ``go strings.HasPrefix(targetPath, destdirClean) `` This does not enforce a path separator boundary. If the destination directory is /tmp/.../context, a tar entry such as ../context-outside/payload.txt cleans to /tmp/.../context-outside/payload.txt and still passes the prefix check. qbee-agent then creates the outside directory and writes the payload outside the intended extraction root. The issue is reachable through the Docker Compose build context path when UseContext is enabled. ## Details Code references below were verified against qbee-io/qbee-agent commit: - 1d8bdbb7422adb4ca563d3114cbe2817d6ba3581 Af…
Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
·GitHub Advisories
### Impact The writer option of the i18nTextCollectorTask dev task was passed to the injector without validation. A crafted dev task URL could create arbitrary objects with attacker-controlled constructor arguments and run code on the server. Because the dev task did not ask for confirmation, an administrator could be tricked into running it by following a link. On a site in dev mode, no login was needed. CMS 5 is not affected. ### Reported by Jack Wallace
Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
·GitHub Advisories
### Impact A user who can edit a record through a GridField detail form could change the record to an unrelated class, without the permission checks for that class. ### Reported by Lachlan Davidson, Carapace
### Impact A user with access to the Security section (CMS_ACCESS_SecurityAdmin) but without the ADMIN permission could edit a group that grants ADMIN through a role or a parent group, and use it to escalate their own privileges. ### Reported by Lachlan Davidson, Carapace
### Impact A CMS user who can edit records through a GridField detail form could create new records without the permission to create them, by sending a save request directly. ### Reported by HDWSec - https://hdwsec.fr
### Impact The HTML sanitiser did not remove SVG data URIs. A CMS author could store content that runs JavaScript in the browser of another user who views it. ### Reported by HDWSec - https://hdwsec.fr
### Impact The HTML sanitiser did not remove XHTML and XML data URIs. A CMS author could store content that runs JavaScript in the browser of another user who views it. ### Reported by Jack Wallace from Bastion Security
Directus: Share update allows reassigning user_created and role
·GitHub Advisories
### Summary A non-admin user who can update their own shares can reassign a share's creator (user_created), role, item, and collection fields after the share is created. The update is authorized against the row as it existed before the change, and the resulting row is never revalidated, so these fields can be set to values the user would not be permitted to assign when creating a share. By reassigning both user_created and role to an administrator the share's effective permissions get elevated. This is a server-side authorization gap in the share update path. It does not by itself produce an administrator token. It re-opens a previously patched privilege-escalation surface on the effective permissions of a share. ### Prerequisites - An authenticated non-admin account that hold…
mail-parser: One hostile attachment aborts `write_attachments()` and silently drops the rest of the batch
·GitHub Advisories
### Impact write_attachments() called _safe_attachment_filename() and write_sample() inside its loop with no guard, so a single crafted attachment raised out of the whole save. Every attachment **after** the malicious one was silently never written, with no error surfaced to a caller that catches only MailParserError. That is an evasion primitive as much as an availability bug: a sender puts one poisoned part first and the real payload second, and the payload never reaches the extraction directory that a downstream scanner or sandbox reads — while it still reaches the recipient's mail client intact. The tool's output diverges from the bytes actually in the message, which is the same failure mode as the filename-sanitizing bypass in [GHSA-fr3h-cpq2-9496](https://github.com/SpamScop…
mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
·GitHub Advisories
### Impact A Received header whose trailing date carries an out-of-range year, or a timezone offset large enough to push the timestamp past the int64 epoch range, raises an exception that is **outside the MailParser* hierarchy**. A caller that catches only mail-parser exceptions does not catch it, and the parse of the entire message is aborted — the same class of issue as [GHSA-24mq-4vc6-2prf](https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf), which this survives (it is not a duplicate; 24mq is fixed in 4.6.2 and this reproduces on 4.6.2). All entry points are affected: parse_from_string(), parse_from_bytes(), parse_from_file(), parse_from_file_obj() and the mail-parser CLI. The header is fully attacker-controlled and a single line is enough,…
Kubeshark: MCP `download_file` writes fetched bytes to an unvalidated destination path
·GitHub Advisories
**Ecosystem / package:** Go — github.com/kubeshark/kubeshark (the kubeshark CLI, kubeshark mcp subcommand) **Affected component:** cmd/mcpRunner.go, MCP tool download_file **Affected versions:** >= v53.1.0, < v53.4.0 (the flaw shipped with the tool's first release; v53.3.0 was the last affected release) **Patched version:** v53.4.0 **Credit:** novice-22 (Urim), via private coordinated disclosure. ## Summary The download_file MCP tool fetches a caller-supplied path from the Kubeshark Hub API and writes the response body to a caller-supplied dest on the local filesystem with no validation of dest. An attacker who can influence the MCP tool arguments — e.g. via indirect prompt injection against an AI agent driving kubeshark mcp — can write attacker-controlled bytes…
**Ecosystem / package:** Go — github.com/kubeshark/kubeshark (the kubeshark CLI, kubeshark mcp subcommand) **Affected component:** cmd/mcpRunner.go, MCP tool start_kubeshark **Affected versions:** >= v53.1.0, < v53.4.0 (the flaw shipped with the MCP command's first release; v53.3.0 was the last affected release) **Patched version:** v53.4.0 **Credit:** novice-22 (Urim), via private coordinated disclosure. ## Summary The start_kubeshark MCP tool builds a kubeshark tap command by appending the caller-supplied pod_regex as a bare positional argument, with no -- end-of-options separator. Because tap is a cobra command, a pod_regex that begins with -/--set= is parsed as a **flag**, not as the pod regex. An attacker who can influence the tool arguments (e.g. indi…
mail-parser: Uncaught exceptions and silent header loss in mail-parser on attacker-controlled input
·GitHub Advisories
### Impact Two effects, sharing the root cause of Advisory 1 — header names chosen by the sender were resolved through Python attribute lookup and rewritten before lookup. **Uncaught exceptions.** A crafted message raises an exception that is *outside* the MailParser* hierarchy, so a caller catching only mail-parser exceptions does not catch it and the worker dies. *Header named after a method* (CWE-248, reported by @iam-niranjan). Python resolves real class attributes before __getattr__, so a header named after a method put a bound method object into the parsed mail dict. A 12-byte email is sufficient. Nine colliding names were confirmed: Parse, Message, Write_Attachments, From_File, From_File_Obj, From_File_Msg, From_String, From_Bytes, Get_Server_Ipaddress. Also r…
mail-parser: Sender IP address spoofing in get_server_ipaddress()
·GitHub Advisories
### Patches Fixed in **4.6.2**. Upgrade with pip install --upgrade mail-parser. Candidate addresses are now selected by position, not by appearance — a bracketed address the sender wrote is byte-identical to one the MTA wrote, so no amount of pattern matching can tell them apart: - the first token of the from clause is the HELO name, whatever its shape, and is never a candidate; - an explicit HELO marker inside a comment group is sender text and is excluded; - a candidate must sit inside a ( / [ group; - IPv4 and IPv6 matches are merged positionally, never family-first; - the walk stops at the first trusted hop naming no address, rather than continuing into sender-written headers. The IPv6 pattern was corrected to skip the IPv6: tag and to prefer the longest valid form. **Behavi…
mail-parser is vulnerable to polynomial ReDoS in email header parsing
·GitHub Advisories
### Summary Two regular expressions used while parsing email headers backtrack polynomially on attacker-controlled input. Parsing a single small, well-formed email can consume minutes to hours of CPU, denying service to any process that parses untrusted mail. Both are reachable from an ordinary parse_from_string(), parse_from_bytes() or parse_from_file() call — no special API, option, or malformed structure is required by the victim. ### Details **1. Address-header fallback regex (src/mailparser/utils.py)** get_addresses() falls back to _ADDR_FALLBACK_RE whenever email.utils.getaddresses(strict=True) yields no usable address. The alternative ([^ overlaps a lazy quantifier with an adjacent \s* — a space matches both. Driven by finditer, which retries at every offset and…
mail-parser: Path Traversal vulnerability in attachment extraction
·GitHub Advisories
A path traversal vulnerability was identified in mail-parser when extracting email attachments using the write_attachments() and write_sample() APIs. A specially crafted email containing malicious attachment filenames (for example, using directory traversal sequences such as "../" or absolute filesystem paths) could cause files to be written outside the intended output directory. Depending on how the library was used and the permissions of the executing process, this could result in arbitrary file overwrite. The vulnerability affects mail-parser versions 3.8.0 through 4.5.0. The issue has been addressed by introducing comprehensive filename sanitization and path validation before any file is written to disk. The fix includes: - Sanitization of attachment filenames before writing. - Valida…
termux-sync: Arbitrary file write during restore via attacker-controlled manifest source path
·GitHub Advisories
termux-sync restore trusts fields inside an untrusted backup manifest and uses them as the extraction destination without validation. During restore, each archive entry is handled as: src_dir = Path(info.get("source", ...)).parent extract_archive(archive, src_dir, ...) extract_archive opens the archive and runs tarfile.extract for every member with no path jail and no filter: with tarfile.open(archive_path, "r:*") as tf: for member in tf.getmembers(): tf.extract(member, dest_path, set_attrs=True) There is no check that manifest "source" stays under an expected restore root, that tar members stay inside dest_path, or that backup_name used in temporary paths cannot contain ".." or separators. Impact: A victim who restores a malicious backup (local, shared, or from a compromised GitHub/Googl…
code-review-mcp-server: Command injection via unsanitized folderPath/baseBranch parameters
·GitHub Advisories
### Impact code-review-mcp-server exposes MCP tools (getLocalGitDiff, codeReview, createPR, getPRTemplate) that accept folderPath and baseBranch string parameters. These caller-controlled values were interpolated directly into shell command strings executed via child_process.execSync(), which runs commands through /bin/sh. A crafted value such as baseBranch = "main; #" (or a $(...) command substitution, or a folderPath that breaks out of the surrounding quotes) results in **arbitrary command execution** on the host running the MCP server. ### Patches Fixed in **1.5.3**. Every execSync() call was replaced with execFileSync() using argument arrays, so inputs are passed directly to git / gh without going through a shell, eliminating the injection at its root.…
### Summary LightSaml 5.0.0 (latest release; also confirmed on 4.6.1) validates an inbound samlp:Response by collecting its direct-child saml:Assertion elements and validating each one's ds:Signature via robrichards/xmlseclibs. The two layers disagree on which element a signature actually covers: LightSaml reads claims from the assertion node it collected, while xmlseclibs resolves the signed Reference URI="#id" with a document-wide //*[@Id] XPath that returns the first ID-bearing element anywhere in the document. An attacker who has captured one genuine signed assertion can exploit this to surface attacker-authored, unsigned claims. ### Details Response::deserialize collects assertions with manyElementsFromXml, whose relative XPath saml:Assertion matches only direct child…