Git LFS versions from 1.3.0 up to 2.13.3 and from 3.0.0 up to 3.8.0 contain a vulnerability where crafted .lfsconfig files in malicious repositories can cause Git LFS to execute arbitrary commands. This occurs because Git LFS does not properly restrict configuration options in .lfsconfig files, allowing attackers to specify custom commands for object transfer. The issue is fixed in version 3.8.1. Users should upgrade to this version and avoid cloning repositories from untrusted sources. No effective workaround exists other than disabling Git LFS.
Git LFS versions from 0.6.0 up to 2.13.3 and from 3.0.0 up to but not including 3.8.1 contain a vulnerability where malicious Git configuration options with embedded line-ending control characters can cause arbitrary command execution during object fetches. This occurs due to improper parsing of submodule configuration options. The issue is fixed in version 3.8.1. Users should upgrade to 3.8.1 or apply workarounds by disabling submodule fetching and deinitializing existing submodules.
OpenRemote versions prior to 1.31.0 contain a vulnerability in the disconnectUserSession endpoint that allows any authenticated user from any realm to forcibly disconnect MQTT sessions belonging to users in other realms without authorization. This occurs because the realm parameter is ignored and no authorization or realm-boundary checks are performed. The endpoint uses an HTTP GET method for a destructive action, increasing risk of CSRF attacks. The vulnerability can disrupt IoT device connectivity across tenant boundaries, impacting building management and industrial IoT deployments.
This security news roundup covers multiple cybersecurity incidents and developments including cyberattacks on Norwegian energy firms, a supercomputer hack in Japan, malware targeting Common Access Cards on personal computers, and the disclosure of an unpatched Windows 11 lock screen bypass exploit. It also reports on EU cyber sanctions against the pro-Russian group NoName057(16), arrests related to ransomware gangs, and data exposures from compromised vendors and test environments. The incidents vary in impact and scope, with some involving data exposure and others involving attempted intrusions without confirmed data loss.
In Postgres Enterprise Manager (PEM), any PEM user can run the pem.send_webhook() function, which runs with elevated privileges and queues a payload for any configured webhook. The PEM agent then delivers it with that webhook's stored headers, OAuth token or client certificate, so a user can send forged notifications to endpoints they could not otherwise authenticate to.
From PEM 10.6.1, no PEM login role can call this function directly. PEM still sends webhook notifications through its own internal paths.
In Postgres Enterprise Manager (PEM), the pem.deploy_job_template() function does not check that the caller can access the servers, groups and agents it deploys a job template to. When PEM teams are used to separate access, a user with the scheduled tasks role (pem_manage_schedule_task) can deploy and schedule SQL or shell job steps on agents that belong to other teams.
From PEM 10.6.1, PEM checks team access for every server, group and agent a template is deployed to.
Paymenter versions prior to 1.5.7 contain a vulnerability in Livewire components where an unauthenticated attacker can invoke any public method via the executeConfirmedAction function. This allows bypassing authorization and modifying protected server-side state, including locked data. The issue arises because executeConfirmedAction dispatches calls to any existing method without sufficient access control. The vulnerability has been fixed in version 1.5.7.
In Postgres Enterprise Manager (PEM), any PEM user can read the encrypted passwords that PEM agents use to connect to monitored servers, including the PEM backend superuser password stored when the PEM server is configured. Unless a custom encryption key is configured, these passwords are encrypted with a key that is the same in every PEM installation, so they can be decrypted.
From PEM 10.6.1, PEM users can no longer read these passwords.
In Postgres Enterprise Manager (PEM), webhook URLs are not validated, and the PEM agent does not restrict the URL schemes it uses to deliver webhooks. A user with the alert configuration role (pem_config_alert) can set up a webhook with a file:// URL. When the webhook is sent, the agent on the PEM server, which runs as root by default, reads the local file and stores its contents in the webhook error record in the PEM database, where any PEM user can read it.
From PEM 10.6.1, PEM accepts and sends only http and https webhook URLs.
In Postgres Enterprise Manager (PEM), the SQL Profiler save and load functions in the PEM web application do not keep the client-supplied file name inside the user's storage directory. A user with the SQL Profiler role (pem_comp_sqlprofiler) can read JSON files, and overwrite files that the PEM web server account can write, outside their own storage directory. Overwriting the PEM web application's configuration database stops the web console for all users.
From PEM 10.6.1, the SQL Profiler only reads and writes files inside the user's storage directory.
In Postgres Enterprise Manager (PEM), multi-factor authentication (MFA) is not enforced on the PEM web application's own routes. An attacker who knows the password of a user who has enrolled a second factor can skip the second factor and call PEM's pages and APIs directly, with that user's permissions. A similar issue in pgAdmin 4 was assigned CVE-2024-4215.
From PEM 10.6.1, every authenticated PEM route requires a completed MFA check.
In Postgres Enterprise Manager (PEM), several SECURITY DEFINER functions in the pem schema of the PEM backend database are owned by a superuser but do not set a safe search_path. Any PEM user who can connect to the PEM backend database can create objects that these functions use in place of the intended ones, and so run arbitrary SQL with superuser privileges. Temporary objects can be used for this on every supported PostgreSQL version, and objects in the public schema on PostgreSQL 14 backends and backends upgraded from PostgreSQL 14.
From PEM 10.6.1, these functions run with a fixed search_path.
In Postgres Enterprise Manager (PEM), the row-level security policies on pem.job and pem.jobstep that apply to PEM agents do not limit an agent to its own jobs. An attacker who controls one monitored host, and so its PEM agent certificate, can create, change or delete jobs for every other agent, including the agent on the PEM server. Agents run SQL job steps with the database credentials of the server they monitor, and shell job steps where batch jobs are enabled, so compromising one monitored host can give superuser SQL access to every monitored database and to the PEM backend.
From PEM 10.6.1, PEM agents can no longer create jobs or change job definitions or job steps.
In Postgres Enterprise Manager (PEM), the pem_agent role, which every PEM agent login inherits, is a member of the PostgreSQL pg_read_server_files and pg_write_server_files roles on the PEM backend database. An attacker who controls any monitored host, and so its PEM agent certificate, can read and write files on the PEM server host as the postgres operating system user. This includes the PEM certificate authority key, which lets the attacker issue certificates for other agents and act as them.
From PEM 10.6.1, PEM agents no longer hold these roles.
storyblok-backup versions prior to 0.7.1 contain a stored path traversal vulnerability. This occurs because component names, which are user-editable and unsanitized, are used directly as filenames during backup creation. An attacker with component management access can craft a component name with path traversal sequences to cause files to be written outside the intended backup directory when the backup tool is run. This can lead to arbitrary file writes on the backup host machine.
The amqtt package versions 0.11.0 through 0.12.0 contain a denial-of-service vulnerability due to a memory leak in the handling of incomplete MQTT QoS 2 transactions. When clients initiate QoS 2 handshakes but disconnect before completion, the broker retains transaction state indefinitely, causing unbounded memory growth. This can lead to broker process termination and loss of availability. The issue is patched in version 0.12.1.
Red Hat Ansible Automation Platform 2.6 received a container release update addressing multiple security issues. The platform enables enterprise IT automation management and sharing of automation content. This update fixes numerous vulnerabilities identified by various CVEs and bugzilla reports.
Poweradmin versions 4.0.0 through before 4.2.6, 4.3.0 through before 4.3.5, and 4.4.0 through before 4.4.1 use a six-digit email second factor code generated with PHP's mt_rand(), a non-cryptographically secure RNG, and do not limit the number of verification attempts. This allows an attacker who has the user's password to brute-force the second factor code within its validity window, defeating the purpose of MFA. Fixes addressing both the RNG and attempt limiting are available in versions 4.2.6, 4.3.5, and 4.4.1.
Fabio contains an access-control bypass vulnerability due to its use of unnormalized request paths for route selection. Variants of protected paths using dot-segments, encoded dots, or double slashes bypass per-route ACL and basic authentication gates, allowing unauthenticated access to protected resources. The vulnerability affects versions prior to 1.7.3 and is confirmed with real-world testing. A fix is available in version 1.7.3.
A Path Traversal vulnerability in workspace directory handling and Git integration in Google Cloud Dataform, BigQuery Studio and Colab Enterprise on Google Cloud Platform allows an authenticated remote attacker to read private files and create arbitrary files across tenant repositories using crafted workspace operations and Git integration requests.
This vulnerability was patched on 10 October 2026, and no customer action is needed.