Michael Holmquist

AppFlowy-Cloud versions 0.7.2 through 0.9.64 fail to authorize callers against the workspace in the bulk publish endpoint path, allowing authenticated users to publish content into other tenants' namespaces. Attackers can write published views with attacker-controlled title, body and metadata into victim workspaces to deface public pages or host phishing content on trusted URLs.

CVE-2026-86095 | Unidata netcdf-c has an out-of-bounds write in NC4 HDF5 inq attname()—crafted HDF5 files overflow a 256-byte buffer, causing memory corruption or crashes. CVSS 7.8. Unpatched. Update immediately. https://t.co/VlVja4g3IT #valtersit #CVE #CVEAlert #infosec #SysAdmin #cybersecurity #Linux #devsecops #devops #developer #sysadmin #100daysofcode #git #github #gitlab #redteam #blueteam #ethicalhacker #ethicalhacking #cybersecurityawareness #cybersecurity #cybersecuritynews #cybersecuritytips #python #hacker #linux #kali #ubuntu #debian #ukraine #spain #ireland #unitedkingdom #canada #finland #estonia #lithuania #ireland #hungary #denmark #norway #malta #mexico #switczerland #china #france #germany #docker #kali

**Name of the Vulnerable Software and Affected Versions** Memos versions 0.26.0 through 0.30.0 **Description** The software fails to revoke refresh tokens when a user changes their password, which allows unauthorized parties to maintain account access. An attacker possessing a stolen refresh token can call the `RefreshToken` RPC to obtain new access tokens and rotate the refresh token indefinitely, bypassing the security measure intended to terminate sessions upon a password change. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** ModelScope versions prior to 1.40.1 **Description** ModelScope uses PyYAML's unsafe `yaml.Loader` to parse model configuration files. This allows arbitrary code execution through Python object construction tags, enabling attackers to craft malicious model repositories with poisoned configuration files that execute code when loaded by users. **Recommendations** Update ModelScope to version 1.40.1 or later.

**Name of the Vulnerable Software and Affected Versions** Dolibarr versions 10.0.0 through 23.0.0 **Description** Authenticated users can retrieve group memberships of other users because the software fails to perform per-object authorization checks. By calling the 'GET /users/{id}/groups' API endpoint with arbitrary `id` values, an attacker can access group names, entity associations, and private notes across tenant boundaries. **Recommendations** Update to version 24.0.0 or later. Restrict access to the 'GET /users/{id}/groups' API endpoint to minimize the risk of unauthorized data retrieval.

**Name of the Vulnerable Software and Affected Versions** Frappe Framework development builds (affected versions not specified) **Description** An authorization flaw exists in the '/render jinja template' endpoint. Low-privileged users can render arbitrary Jinja templates by providing raw template strings. This allows attackers who possess print permissions on any document to execute arbitrary SELECT statements against unrelated tables, which can lead to the exposure of password hashes from the ` Auth` table. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Dolibarr versions prior to 24.0.0 **Description** A SQL injection exists in the CSV and XLSX import wizard. The issue occurs because the wizard reads update keys using the `GETPOST('updatekeys','array')` function in `htdocs/imports/import.php`, applying only a filter that removes HTML while leaving SQL keywords, quotes, and parentheses intact. Subsequently, the `import insert()` function in `htdocs/core/modules/import/import csv.modules.php` builds a filter where the `$where[]` variable is constructed using the submitted keys without proper validation against a legitimate list of column codes. This allows a user with import permissions to use a `UNION SELECT` statement to exfiltrate arbitrary table content or redirect which row is overwritten during an update. The vulnerability is triggered when the assembled string is executed via `$this->db->query()`. **Recommendations** Update to version 24.0.0 or later. As a temporary mitigation, restrict import permissions to only trusted users.

**Name of the Vulnerable Software and Affected Versions** darknet (affected versions not specified) **Description** An out-of-bounds read and write occurs when the software subscripts its layer array using an index from a configuration file without verifying it against the array length. The array is allocated in `src-lib/darknet network.cpp` based on the number of layer sections declared. Specifically, the `from` field in shortcut, scale channels, and sam sections, and the `layers` field in the route section, provide indices that are used in `parse shortcut section` within `src-lib/darknet cfg.cpp` to read `net.layers[index].outputs` without bounds checking. Subsequently, the dispatch loop in `create network` uses the same index to assign values to `net.layers[l.index].use bin output` and `net.layers[l.index].keep delta gpu`, resulting in a write operation past the allocation. Processing a specially crafted configuration file can lead to a reliable system crash. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Baserow versions prior to 2.3.1 **Description** Baserow fails to act on the result of a permission check when dispatching an Application Builder data source. The dispatch and record-name views in `backend/src/baserow/contrib/builder/api/data sources/views.py` use a permission class that allows any caller, enabling unauthenticated requests to reach the handler. Subsequently, the `DataSourceService.dispatch data sources` function in `backend/src/baserow/contrib/builder/data sources/service.py` calls `check multiple permissions()` without requiring it to raise an exception and ignores the returned mapping of denials. Consequently, the data source is dispatched using the integration's own credentials regardless of the caller's identity, allowing unauthenticated users to retrieve rows and fields by enumerating small integer identifiers. **Recommendations** Update to version 2.3.1.

**Name of the Vulnerable Software and Affected Versions** Dolibarr versions prior to 23.0.4 **Description** An incorrect authorization check in the REST API allows authenticated users to delete documents using insufficient permissions. The `Documents::delete()` function in `htdocs/api/class/api documents.class.php` calls `dol check secure access document()` using the `read` mode instead of the `write` mode when processing the `DELETE /api/index.php/documents` endpoint. Consequently, a user with only read permissions for a module (such as `societe:lire` or `facture:lire`) can permanently delete files, including invoices, orders, proposals, project files, and generated PDFs, without having create, write, delete, or admin privileges. **Recommendations** Update to version 23.0.4 or later.

**Name of the Vulnerable Software and Affected Versions** Dolibarr versions 9.0.0 through 23.0.4 **Description** The software saves inbound email attachments using the name provided in the message's MIME headers without properly sanitizing it to a safe basename. This occurs within the global `saveAttachment()` function in htdocs/emailcollector/lib/emailcollector.lib.php, which constructs `$filepath` using `$path`, `$filename`, and `$ext` before passing it to `file put contents()`, and the private `saveAttachment()` function in htdocs/emailcollector/class/emailcollector.class.php, which writes to `$destdir` using `$filename`. These values are derived from the attachment's `getName()` or `getFilename()` during record-join, create-ticket, and create-project operations. An attacker can include a traversal sequence in the filename to place controlled content outside the intended attachment directory without requiring an account. If the htdocs directory is read-only, the impact is limited to the documents tree, potentially corrupting or forging other objects' documents. However, if htdocs is writable, the attacker can write files to a web-executable path. **Recommendations** Update to version 24.0.0.

**Name of the Vulnerable Software and Affected Versions** Frappe versions 15.11.0 through 16.32.0 **Description** The software stores and renders workspace card descriptions without Cross-Site Scripting (XSS) filtering. This occurs because the description field of the Workspace Link doctype is configured to ignore XSS filters, causing the ` sanitize content()` function in `frappe/model/base document.py` to store the submitted value without sanitization. Subsequently, the `LinksWidget.set body()` function in `frappe/public/js/frappe/widgets/links widget.js` interpolates this content into a Bootstrap popover without HTML escaping. A user with the Workspace Manager role can inject arbitrary markup into a public workspace card description. This markup executes in the session of any user who hovers over the description, potentially allowing session token theft and unauthorized authenticated requests. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Vocos (affected versions not specified) **Description** The software instantiates classes based on a configuration file without restricting which classes can be named. The `instantiate class` function in `vocos/pretrained.py` uses the `class path` value from the configuration to import a module via ` import ` and resolve an attribute using `getattr`, subsequently calling the result as `args class(*args, **kwargs)` with arguments from the `init args` mapping. Because there is no allowlist to constrain the dotted path, a configuration file can specify any importable callable and its arguments. This issue is reachable through `Vocos.from hparams` for `feature extractor`, `backbone`, and `head` entries, as well as through `Vocos.from pretrained`, which downloads a `config.yaml` from a specified Hugging Face repository. Consequently, loading a model from an untrusted repository allows the repository owner to execute arbitrary code during the loading process. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Flair versions 0.15.0 through 0.15.1 **Description** An issue exists in the `flair/models/clustering.py` file where the `ClusteringModel.load()` static method uses `pickle.loads()` on a file loaded via `joblib.load()`. This allows for the execution of arbitrary Python code when a maliciously crafted model file is loaded, granting the attacker the privileges of the process performing the load. **Recommendations** For versions 0.15.0 through 0.15.1, avoid importing `flair.models.clustering` and do not use the `ClusteringModel.load()` function to load untrusted model files.

**Name of the Vulnerable Software and Affected Versions** Hugo versions 0.91.0 through 0.165.0 **Description** An issue exists in the `security.http.urls` allowlist which serves as the sole control for outbound fetches performed by `resources.GetRemote`. The `CheckAllowedHTTPURL` function in `config/security/securityConfig.go` validates the URL text and canonicalized IPv4 hosts but fails to resolve hostnames or inspect the actual destination address the HTTP client connects to. Additionally, the client in `resources/resource factories/create/create.go` lacks a dial-time hook, meaning no validation occurs during the connection phase. Consequently, a hostname resolving to a loopback, private, or cloud-metadata address can bypass the policy. An attacker capable of providing a URL through content, such as a CMS field or front-matter field, can force the build process to fetch data from an internal endpoint and include the response in the static output, leading to Server-Side Request Forgery (SSRF). **Recommendations** Update Hugo to a version later than 0.165.0. As a temporary mitigation, restrict the ability for untrusted users to provide URLs via front-matter or CMS fields used by `resources.GetRemote`.

**Name of the Vulnerable Software and Affected Versions** RustDesk (affected versions not specified) **Description** Windows clipboard redirection fails to perform an upper bound check when copying a peer-supplied length into a fixed-size caller buffer. When an OLE paste consumer, such as explorer.exe, calls `IStream::Read` with a buffer of `cb` bytes, the `CliprdrStream Read` function in `libs/clipboard/src/windows/wf cliprdr.c` requests data via `cliprdr send request filecontents` and executes `CopyMemory(pv, clipboard->req fdata, clipboard->req fsize)`. The `req fsize` variable is taken directly from the peer's CLIPRDR FileContentsResponse via `wf cliprdr server file contents response` and is not clamped to `cb`. Because the length comparison `req fsize < cb` occurs after the copy operation, a malicious peer can send an oversized response to write arbitrary data past the end of the paste consumer's heap buffer when a local user pastes clipboard file contents from a remote side. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.

**Name of the Vulnerable Software and Affected Versions** Hugo versions 0.93.0 through 0.165.0 **Description** The default fenced-code-block renderer fails to escape attribute values derived from the code-fence info string when writing them to the rendered HTML. This occurs because the `New` function in `markup/internal/attributes/attributes.go` converts attribute values from byte slices to strings, bypassing the escaping process. Subsequently, the `RenderAttributes()` function only escapes values that remain as byte slices, meaning string values are written verbatim. An attacker can use a quote within an attribute value to terminate the attribute and inject additional attributes, such as event handlers, into the wrapper element, leading to stored Cross-Site Scripting (XSS). This issue is present in the default configuration when code fences are enabled, regardless of the goldmark unsafe setting or custom render hooks. While attribute names starting with `on` are filtered during parsing, injection is still possible via the attribute value. **Recommendations** Update Hugo to a version later than 0.165.0.

**Name of the Vulnerable Software and Affected Versions** Craftplan versions prior to 0.5.1 **Description** Broken access control allows unauthenticated attackers to read sensitive credentials by exploiting an unconditional authorization policy on the Settings resource. By sending a GET request to the settings API endpoint with a valid record ID, attackers can retrieve decrypted SMTP passwords, email API keys, and email API secrets. This occurs because the read policy uses an always-allow authorization check that bypasses all identity verification. **Recommendations** Update Craftplan to version 0.5.1 or later.

**Name of the Vulnerable Software and Affected Versions** Hugo versions 0.162.0 through 0.164.x **Description** A flaw exists in the Node.js permission model implementation where the tool `tailwindcss` is added to the default `AllowChildProcess` list. This allows the `tailwind.config.js` file to execute top-level code that can call `child process` to spawn a shell. Because the spawned process is not a Node process, it does not inherit permission flags and runs with the full privileges of the account performing the build. Consequently, building a site using a theme, module, or starter template with a malicious Tailwind configuration can lead to arbitrary command execution, bypassing the intended file system restrictions. **Recommendations** Update to version 0.165.0 or later. As a temporary mitigation, restrict the use of the `tailwindcss` tool in the security configuration to prevent it from being launched under the default configuration.

**Name of the Vulnerable Software and Affected Versions** NASA core Flight System (cFS) Health and Safety (HS) application versions through 7.0.1 **Description** An incomplete fix for a previous issue leaves a NULL pointer dereference reachable. A NULL pointer dereference occurs when a program attempts to read or write to a memory address that is NULL, which typically leads to a program crash. An attacker who triggers the affected command under specific conditions can cause the HS application to crash, resulting in a denial-of-service condition and processor reset. **Recommendations** At the moment, there is no information about a newer version that contains a fix for this vulnerability.