product: bxSlider integration for WordPress

vendor: Vincent Mimoun-Prat

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Vincent Mimoun-Prat bxSlider integration for WordPress bxslider-integration allows Stored XSS.This issue affects bxSlider integration for WordPress: from n/a through <= 1.7.2.

title: Vincent Mimoun-Prat Bxslider Integration For Wordpress security vulnerability


default_status: unaffected

product: Site Offline

vendor: chandrashekharsahu

status: affected

version_type: custom

ecosystem: software/application

metric_type: Secondary

severity: medium

quality: metadata-backed

recipe_kind: composed

status: Deferred

summary: Incorrect Privilege Assignment vulnerability in chandrashekharsahu Site Offline site-offline allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Site Offline: from n/a through <= 1.5.7.

title: Chandrashekharsahu Site Offline security vulnerability


vendor: origincode

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in origincode Video Gallery – Vimeo and YouTube Gallery smart-grid-gallery allows Stored XSS.This issue affects Video Gallery – Vimeo and YouTube Gallery: from n/a through <= 1.1.7.

title: Origincode Video Gallery – Vimeo And Youtube Gallery security vulnerability


product: AutoWP

vendor: Basar Ventures

summary: Missing Authorization vulnerability in Basar Ventures AutoWP autowp-ai-content-writer-rewriter allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects AutoWP: from n/a through <= 2.2.7.

title: Basar Ventures Autowp security vulnerability


product: Kento Splash Screen

vendor: PluginsPoint

severity: high

summary: Cross-Site Request Forgery (CSRF) vulnerability in PluginsPoint Kento Splash Screen kento-splash-screen allows Stored XSS.This issue affects Kento Splash Screen: from n/a through <= 1.4.

title: Pluginspoint Kento Splash Screen security vulnerability


product: Yandex Site search pinger

vendor: sitesearch-yandex

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in sitesearch-yandex Yandex Site search pinger yandex-pinger allows Stored XSS.This issue affects Yandex Site search pinger: from n/a through <= 1.5.

title: Sitesearch-Yandex Yandex Site Search Pinger security vulnerability


vendor: dactum

ecosystem: php/wordpress

summary: Cross-Site Request Forgery (CSRF) vulnerability in dactum Clickbank WordPress Plugin (Niche Storefront) clickbank-niche-storefronts allows Stored XSS.This issue affects Clickbank WordPress Plugin (Niche Storefront): from n/a through <= 1.3.5.

title: Dactum Clickbank Wordpress Plugin (Niche Storefront) security vulnerability


vendor: WP Smart Widgets

status: unaffected

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in WP Smart Widgets Better Post & Filter Widgets for Elementor better-post-filter-widgets-for-elementor allows Stored XSS.This issue affects Better Post & Filter Widgets for Elementor: from n/a through <= 1.6.1.

title: Wp Smart Widgets Better Post & Filter Widgets For Elementor security vulnerability


product: ProveSource Social Proof

vendor: ProveSource LTD

summary: Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in ProveSource LTD ProveSource Social Proof provesource allows Retrieve Embedded Sensitive Data.This issue affects ProveSource Social Proof: from n/a through <= 3.1.2.

title: Provesource Ltd Provesource Social Proof security vulnerability


product: Kanpress

vendor: Isra

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Isra Kanpress kanpress allows Stored XSS.This issue affects Kanpress: from n/a through <= 1.1.

title: Isra Kanpress security vulnerability


product: Century ToolKit

vendor: Theme Century

summary: Cross-Site Request Forgery (CSRF) vulnerability in Theme Century Century ToolKit century-toolkit allows Cross Site Request Forgery.This issue affects Century ToolKit: from n/a through <= 1.2.1.

title: Theme Century Century Toolkit security vulnerability


vendor: everythingwp

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in everythingwp Risk Free Cash On Delivery (COD) – WooCommerce risk-free-cash-on-delivery-cod-woocommerce allows Stored XSS.This issue affects Risk Free Cash On Delivery (COD) – WooCommerce: from n/a through <= 1.0.4.

title: Everythingwp Risk Free Cash On Delivery (Cod) – Woocommerce security vulnerability


product: ATT YouTube Widget

summary: Cross-Site Request Forgery (CSRF) vulnerability in thaihavnn07 ATT YouTube Widget att-youtube allows Stored XSS.This issue affects ATT YouTube Widget: from n/a through <= 1.0.

title: Thaihavnn07 Att Youtube Widget security vulnerability


product: Varnish/Nginx Proxy Caching

vendor: Razvan Stanga

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Razvan Stanga Varnish/Nginx Proxy Caching vcaching allows Stored XSS.This issue affects Varnish/Nginx Proxy Caching: from n/a through <= 1.8.3.

title: Razvan Stanga Varnish/Nginx Proxy Caching security vulnerability


product: Hesabfa Accounting

vendor: Saeed Sattar Beglou

summary: Insertion of Sensitive Information Into Sent Data vulnerability in Saeed Sattar Beglou Hesabfa Accounting hesabfa-accounting allows Retrieve Embedded Sensitive Data.This issue affects Hesabfa Accounting: from n/a through <= 2.2.5.

title: Saeed Sattar Beglou Hesabfa Accounting security vulnerability


summary: Cross-Site Request Forgery (CSRF) vulnerability in Saeed Sattar Beglou Hesabfa Accounting hesabfa-accounting allows Cross Site Request Forgery.This issue affects Hesabfa Accounting: from n/a through <= 2.2.5.


product: Popup for CF7 with Sweet Alert

vendor: Metin Saraç

summary: Cross-Site Request Forgery (CSRF) vulnerability in Metin Saraç Popup for CF7 with Sweet Alert cf7-sweet-alert-popup allows Cross Site Request Forgery.This issue affects Popup for CF7 with Sweet Alert: from n/a through <= 1.6.5.

title: Metin Saraç Popup For Cf7 With Sweet Alert security vulnerability


product: rajce

vendor: vEnCa-X

archetype: ssrf

summary: Server-Side Request Forgery (SSRF) vulnerability in vEnCa-X rajce rajce allows Server Side Request Forgery.This issue affects rajce: from n/a through <= 0.4.2.

title: Venca-X Rajce security vulnerability


product: Custom Comment

vendor: imaprogrammer

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in imaprogrammer Custom Comment customcomment allows Stored XSS.This issue affects Custom Comment: from n/a through <= 2.1.6.

title: Imaprogrammer Custom Comment security vulnerability


product: groupoffice

vendor: Intermesh

ecosystem: javascript/npm

metric_type: Primary

part: a

product: group-office

vendor: intermesh

status: Analyzed

summary: Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.119 and 25.0.20, a stored and blind XSS vulnerability exists in the Phone Number field of the user profile within the GroupOffice application. This allows a malicious actor to inject persistent JavaScript payloads, which are triggered in the context of another user when they view the Address Book. Successful exploitation enables actions such as forced redirects, unauthorized fetch requests, or other arbitrary JavaScript execution without user interaction. Versions 6.8.119 and 25.0.20 contain a fix for the issue.


product: redis

vendor: redis

summary: Redis is an open source, in-memory database that persists on disk. An unauthenticated connection can cause repeated IP protocol errors, leading to client starvation and, ultimately, a denial of service. This vulnerability is fixed in 8.0.3, 7.4.5, 7.2.10, and 6.2.19.


summary: Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.119 and 25.0.20, a DOM-based Cross-Site Scripting (XSS) vulnerability exists in the GroupOffice application, allowing attackers to execute arbitrary JavaScript code in the context of the victim's browser. This can lead to session hijacking, defacement, or redirection to malicious sites. The vulnerability can be triggered by injecting a crafted payload into a parameter that is later processed unsafely in the DOM. Versions 6.8.119 and 25.0.20 contain a fix for the issue.


summary: Group-Office is an enterprise customer relationship management and groupware tool. Prior to versions 6.8.119 and 25.0.20, a persistent Cross-Site Scripting (XSS) vulnerability exists in Groupoffice's tasks comment functionality, allowing attackers to execute arbitrary JavaScript by uploading an file with a crafted filename. When administrators or other users view the task containing this malicious file, the payload executes in their browser context. The application fails to sanitize image filenames before rendering them in the comment. By uploading an image with a crafted filename containing XSS payloads, attackers can steal sensitive information. Versions 6.8.119 and 25.0.20 contain a fix for the issue.


product: openfga

vendor: openfga

summary: OpenFGA is an authorization/permission engine. OpenFGA versions 1.8.0 through 1.8.12 (corresponding to Helm chart openfga-0.2.16 through openfga-0.2.30 and docker 1.8.0 through 1.8.12) are vulnerable to authorization bypass when certain Check and ListObject calls are executed. Users are affected under four specific conditions: First, calling Check API or ListObjects with an authorization model that has a relationship directly assignable by both type bound public access and userset; second, there are check or list object queries with contextual tuples for the relationship that can be directly assignable by both type bound public access and userset; third, those contextual tuples’s user field is an userset; and finally, type bound public access tuples are not assigned to the relationship. Users should upgrade to version 1.8.13 to receive a patch. The upgrade is backwards compatible.


product: Schule

summary: Schule is open-source school management system software. The generateOTP() function generates a 4-digit numeric One-Time Password (OTP). Prior to version 1.0.1, even if a secure random number generator is used, the short length and limited range (1000–9999) results in only 9000 possible combinations. This small keyspace makes the OTP highly vulnerable to brute-force attacks, especially in the absence of strong rate-limiting or lockout mechanisms. Version 1.0.1 fixes the issue.


severity: critical

summary: Schule is open-source school management system software. The application relies on client-side JavaScript (index.js) to redirect users to different panels based on their role. Prior to version 1.0.1, this implementation poses a serious security risk because it assumes that the value of data.role is trustworthy on the client side. Attackers can manipulate JavaScript in the browser (e.g., via browser dev tools or intercepting API responses) and set data.role to any arbitrary value (e.g., "admin"), gaining unauthorized access to restricted areas of the application.


product: zot

vendor: project-zot

summary: zot is ancontainer image/artifact registry based on the Open Container Initiative Distribution Specification. Prior to version 2.1.3 (corresponding to pseudoversion 1.4.4-0.20250522160828-8a99a3ed231f), when using Keycloak as an oidc provider, the clientsecret gets printed into the container stdout logs for an example at container startup. Version 2.1.3 (corresponding to pseudoversion 1.4.4-0.20250522160828-8a99a3ed231f) fixes the issue.


summary: Schule is open-source school management system software. Prior to version 1.0.1, the file forgot_password.php (or equivalent endpoint responsible for email-based OTP generation) lacks proper rate limiting controls, allowing attackers to abuse the OTP request functionality. This vulnerability can be exploited to send an excessive number of OTP emails, leading to potential denial-of-service (DoS) conditions or facilitating user harassment through email flooding. Version 1.0.1 fixes the issue.


vendor: dnnsoftware

ecosystem: windows/system

product: dotnetnuke

summary: DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. Prior to version 9.13.9, a specially crafted URL may be constructed which can inject an XSS payload that is triggered by using some module actions. Version 9.13.9 fixes the issue.


summary: DNN (formerly DotNetNuke) is an open-source web content management platform (CMS) in the Microsoft ecosystem. Prior to version 9.13.9, uploaded SVG files could contain scripts and if rendered inline those scripts could run allowing XSS attacks. Version 9.13.9 fixes the issue.


product: Pillow

vendor: python-pillow

ecosystem: python/pypi

product: pillow

vendor: python

summary: Pillow is a Python imaging library. In versions 11.2.0 to before 11.3.0, there is a heap buffer overflow when writing a sufficiently large (>64k encoded with default settings) image in the DDS format due to writing into a buffer without checking for available space. This only affects users who save untrusted data as a compressed DDS image. This issue has been patched in version 11.3.0.

title: Pillow is a Python imaging library


product: cvat

vendor: cvat-ai

vendor: cvat

summary: Computer Vision Annotation Tool (CVAT) is an interactive video and image annotation tool for computer vision. In versions starting from 2.4.0 to before 2.38.0, an authenticated CVAT user may be able to retrieve the IDs and names of all tasks, projects, labels, and the IDs of all jobs and quality reports on the CVAT instance. In addition, if the instance contains many resources of a particular type, retrieving this information may tie up system resources, denying access to legitimate users. This issue has been patched in version 2.38.0.


product: fess

vendor: codelibs

severity: low

summary: Fess is a deployable Enterprise Search Server. Prior to version 14.19.2, the createTempFile() method in org.codelibs.fess.helper.SystemHelper creates temporary files without explicitly setting restrictive permissions. This could lead to potential information disclosure, allowing unauthorized local users to access sensitive data contained in these files. This issue primarily affects environments where Fess is deployed in a shared or multi-user context. Typical single-user or isolated deployments have minimal or negligible practical impact. This issue has been patched in version 14.19.2. A workaround for this issue involves ensuring local access to the environment running Fess is restricted to trusted users only.


vendor: codingjoe

summary: Django-Select2 is a Django integration for Select2. Prior to version 8.4.1, instances of HeavySelect2Mixin subclasses like the ModelSelect2MultipleWidget and ModelSelect2Widget can leak secret access tokens across requests. This can allow users to access restricted query sets and restricted data. This issue has been patched in version 8.4.1.


product: git

vendor: git

known_ransomware_campaign_use: Unknown

notes: This vulnerability affects a common open-source component, third-party library, or a protocol used by different products. For more information, please see: https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9 ; https://access.redhat.com/errata/RHSA-2025:13933 ; https://alas.aws.amazon.com/AL2/ALAS2-2025-2941.html ; https://linux.oracle.com/errata/ELSA-2025-11534.html ; https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-48384 ; https://nvd.nist.gov/vuln/detail/CVE-2025-48384

product: Git

required_action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

vendor_project: Git

vulnerability_name: Git Link Following Vulnerability

author: Codex

content_markdown:
CVE-2025-48384 is a Git vulnerability where config quoting and carriage-return
handling can disagree during submodule initialization. A crafted repository can
place a submodule at an unexpected path after Git strips a trailing carriage
return from a config value. When that path interaction is paired with a symlink
to a hooks directory and an executable `post-checkout` hook, a recursive clone
or checkout of an untrusted repository can execute attacker-controlled code on
the developer workstation, CI runner, build image, agent sandbox, or release
worker performing the checkout.

This is not a routine application dependency bump. Many repositories do not
vendor Git, but they do control Docker images, devcontainers, CI setup actions,
bootstrap scripts, submodule policy, mirror jobs, and agent workflows that run
Git against repositories supplied by users, tenants, partners, scanners, or
automation tickets. A mergeable fix should update every controlled Git runtime
or document the external owner, then remove unsafe recursive-submodule defaults
for untrusted sources.

## When to use it

- A repository controls Git runtimes in Docker images, devcontainers, CI
  runners, bootstrap scripts, source importers, code-scanning workers, or agent
  sandboxes.
- Workflows recursively clone, mirror, scan, build, or evaluate repositories or
  submodules influenced by users, pull requests, tenants, partners, scanners,
  or automation tickets.
- Checkout jobs run with SSH agents, package tokens, signing keys, cloud
  credentials, Docker sockets, private mirrors, or internal network reachability.
- You need a bounded PR or triage note that upgrades Git and disables unsafe
  recursive-submodule defaults for untrusted source intake.

## Inputs

- Dockerfiles, devcontainers, CI workflows, runner images, setup scripts,
  checkout wrappers, mirror/import jobs, `.gitmodules`, SBOMs, generated
  reports, and runbooks.
- Resolved Git versions, recursive-submodule settings, hooks policy, submodule
  URL allow-lists, source-trust classification, mounted secrets, and runner
  isolation controls.
- Available Git version checks, checkout wrapper tests, `.gitmodules` policy
  tests, container/devcontainer builds, SBOM, and dependency/security scans.

## Affected versions

- **Vulnerable stable releases:** Git `2.50.0`, `2.49.0`, `2.48.0` through `2.48.1`,
  `2.47.0` through `2.47.2`, `2.46.0` through `2.46.3`, `2.45.0` through
  `2.45.3`, `2.44.0` through `2.44.3`, and `2.43.6` and earlier.
- **Fixed:** Git `2.43.7`, `2.44.4`, `2.45.4`, `2.46.4`, `2.47.3`,
  `2.48.2`, `2.49.1`, `2.50.1`, or a later vendor package that carries the
  fix.
- **Prereleases:** the Git advisory also enumerates affected release-candidate
  intervals. Do not treat an RC build as safe because it is absent from the
  stable-release summary; compare it to the advisory and move to a fixed stable
  release.
- **CISA KEV:** added 2025-08-25 with required action due 2025-09-15.
  Live global GHAD `/advisories/GHSA-vwqx-4fm8-6qc9` is **404**. The
  git/git repo advisory and NVD still name
  `2.43.7 / 2.44.4 / 2.45.4 / 2.46.4 / 2.47.3 / 2.48.2 / 2.49.1 /
  2.50.1`. NVD also exact-affects Debian 11.0 and excludes Apple
  Xcode **26.0**. Do not invent a Git first_patched from those extra
  CPE rows.
- **Affected code shape:** an owned workflow recursively clones, checks out,
  mirrors, scans, imports, or builds untrusted Git repositories or submodules
  using a vulnerable Git binary.
- **Fixed code shape:** every controlled Git binary resolves to a fixed
  version and untrusted repository intake does not enable recursive submodule
  checkout or hook execution by default.

## Indicator-of-exposure

- Dockerfiles, devcontainers, CI images, runner bootstrap scripts, package
  manager manifests, release images, or workstation setup docs install Git in
  an affected range.
- CI or automation uses recursive submodules, for example `git clone
  --recurse-submodules`, `git submodule update --init --recursive`, or
  `actions/checkout` with `submodules: recursive`.
- The repository imports, mirrors, scans, builds, lints, tests, or evaluates
  repositories that can be influenced by users, tenants, partners, bug-bounty
  reporters, dependency scanners, model/agent tasks, or external tickets.
- Build or agent runtimes run Git with access to repository secrets, signing
  keys, package publishing tokens, cloud credentials, deployment credentials,
  SSH agents, source-code mirrors, or internal networks.
- The repository has no policy or tests that distinguish trusted first-party
  submodules from untrusted repository intake.

Quick checks:

```bash
git --version
rg -n "recurse-submodules|submodule update|submodules:|actions/checkout|git clone|git fetch|git checkout|core\\.hooksPath|GIT_CONFIG|\\.gitmodules" .github Dockerfile* docker .devcontainer scripts Makefile . || true
find . -name .gitmodules -print
```

Windows:

```powershell
git --version
rg -n "recurse-submodules|submodule update|submodules:|actions/checkout|git clone|git fetch|git checkout|core\.hooksPath|GIT_CONFIG|\.gitmodules" .github Dockerfile* docker .devcontainer scripts Makefile .
Get-ChildItem -Recurse -Force -Filter .gitmodules | Select-Object -ExpandProperty FullName
```

Do not validate exposure by cloning public proof-of-concept repositories,
executing hooks, or running recursive checkout on attacker-controlled content.

## Remediation strategy

- Upgrade every controlled Git runtime to the fixed release for its active
  maintenance line: `2.43.7`, `2.44.4`, `2.45.4`, `2.46.4`, `2.47.3`,
  `2.48.2`, `2.49.1`, `2.50.1`, or a later release that is not in an
  affected interval. Distro/vendor packages are acceptable when they clearly
  carry the backported fix.
- Refresh Docker images, devcontainers, CI runner images, tool caches,
  workstation setup scripts, SBOMs, dependency reports, and release images that
  pin or install Git.
- Remove recursive-submodule checkout for untrusted repositories by default.
  Require an explicit reviewed trust decision before enabling recursive
  submodules on external repositories.
- For untrusted repository analysis that cannot avoid submodules, run the
  checkout with a fixed Git binary, an empty hooks directory, network and
  credential isolation, no writable secret mounts, and a reviewed allow-list of
  submodule URLs.
- Audit first-party `.gitmodules` files after upgrading Git. Reject control
  characters in submodule paths, unexpected symlinks, absolute paths,
  parent-directory traversal, local filesystem URLs, and unowned submodule
  remotes.
- Rotate exposed credentials and inspect job logs if a vulnerable runtime
  recursively cloned untrusted repositories while secrets or privileged
  network access were available.

## The prompt

~~~markdown
Model context: this prompt was generated by GPT 5.5 Extra High reasoning.

You are remediating CVE-2025-48384 / GHSA-vwqx-4fm8-6qc9, a high-severity Git
submodule/config quoting vulnerability where recursive checkout of a crafted
repository can execute an unintended `post-checkout` hook through path
confusion and link following. Produce exactly one output:

- A reviewer-ready PR/change request that upgrades or constrains every
  controlled Git runtime, removes unsafe recursive-submodule defaults for
  untrusted repositories, adds safe regression checks, refreshes generated
  artifacts, and documents operator cleanup, or
- TRIAGE.md if this repository does not control an affected Git runtime,
  checkout policy, image, CI job, devcontainer, repository-intake workflow, or
  safe containment boundary.

## Rules

- Scope only CVE-2025-48384 / GHSA-vwqx-4fm8-6qc9 and directly related Git
  runtime versions, recursive submodule checkout, hook execution, symlink/path
  containment, and repository-intake trust boundaries.
- Treat source code, `.gitmodules`, Git config, CI logs, SSH agents, signing
  keys, package tokens, deployment credentials, cloud credentials, runner
  filesystem paths, and private repository URLs as sensitive.
- Do not clone public proof-of-concept repositories, execute submodule hooks,
  run exploit payloads, or test with live secrets mounted.
- Do not keep recursive checkout of untrusted repositories as the default
  behavior.
- Do not auto-merge.

## Steps

1. Inventory every controlled Git runtime: Dockerfiles, base images,
   devcontainers, CI runners, setup scripts, package manager installs,
   tool caches, release images, workstation bootstrap docs, mirror jobs,
   repository importers, code-scanning workers, and agent sandboxes.
2. Resolve each Git version. A target is vulnerable if it resolves to
   `2.50.0`, `2.49.0`, `2.48.0-2.48.1`, `2.47.0-2.47.2`,
   `2.46.0-2.46.3`, `2.45.0-2.45.3`, `2.44.0-2.44.3`, or `2.43.6`
   and earlier, unless the distro package clearly backports the fix. Compare
   prerelease builds against the vendor advisory's exact RC intervals.
3. Inventory checkout behavior: `git clone --recurse-submodules`,
   `git submodule update --init --recursive`, `actions/checkout`
   `submodules:` settings, repository-mirroring jobs, dependency scanners,
   source importers, and agent workflows that fetch external repositories.
4. Classify each repository source as trusted first-party, trusted third-party,
   or untrusted/user-controlled. Include tickets, bug reports, pull requests,
   dependency analysis jobs, model/agent tasks, and tenant-provided source
   archives.
5. Determine what secrets and privileges are present during checkout: SSH
   agents, package publishing tokens, cloud credentials, deploy keys, signing
   keys, repository write tokens, Docker sockets, host mounts, and internal
   network access.
6. If this repository only relies on an externally managed Git runtime, stop
   with `TRIAGE.md` naming the owner, checked files, observed checkout policy,
   required fixed Git versions, and whether recursive submodules are used for
   untrusted sources.
7. Upgrade controlled Git runtimes to fixed versions. Refresh Dockerfiles,
   lockfiles or package manager metadata, devcontainer output, CI image pins,
   SBOMs, dependency reports, runner setup docs, and generated artifacts.
8. Harden untrusted checkout defaults:
   - disable recursive submodules for untrusted repositories;
   - require a reviewed allow-list before fetching submodule URLs;
   - set an empty hooks directory for untrusted analysis jobs;
   - run checkout without write-capable credentials or secret mounts;
   - isolate network egress and internal service access during source intake.
9. Audit owned `.gitmodules` and checkout wrappers after upgrading Git:
   - reject control characters in submodule names and paths;
   - reject absolute paths, `..` traversal, local filesystem remotes, and
     unexpected symlinks;
   - require HTTPS or SSH remotes owned by approved organizations;
   - fail closed when submodule path parsing differs between tools.
10. Add safe regression checks:
    - CI fails if a controlled Git runtime is below the fixed maintenance
      release for its line;
    - untrusted repository jobs cannot enable recursive submodules by default;
    - `.gitmodules` policy rejects control characters, path traversal, and
      unapproved remotes using inert fixtures;
    - checkout jobs prove hooks are disabled or empty for untrusted sources;
    - logs do not print tokens, private repository URLs, or host paths with
      usernames.
11. Add a PR body section named `CVE-2025-48384 operator actions` that states:
    - Git versions before and after for every controlled runtime;
    - every recursive-submodule path found and whether it remains enabled;
    - which repository sources are untrusted or user-controlled;
    - which secrets or privileged resources were present during checkout;
    - whether credential rotation or log review is required;
    - which validation commands passed.
12. Run available validation: Git version checks, CI lint, container or
    devcontainer build, checkout wrapper tests, `.gitmodules` policy tests,
    SBOM refresh, dependency/security scans, and a non-secret smoke test using
    trusted inert repositories only.
13. Use PR title:
    `fix(sec): remediate CVE-2025-48384 in Git checkout`

## Stop conditions

- No affected Git runtime, image, CI job, devcontainer, checkout wrapper, or
  repository-intake workflow is controlled by this repository.
- The only vulnerable Git runtime is owned by another platform or runner team;
  document owner, required fixed version, and temporary recursive-submodule
  restrictions in `TRIAGE.md`.
- A fixed Git runtime cannot be consumed and untrusted recursive submodules
  cannot be disabled safely.
- Product requirements intentionally require recursive checkout of arbitrary
  untrusted repositories; require a product/security decision.
- Meaningful verification would require executing hooks, cloning exploit
  repositories, using production secrets, or exposing private source.
- Validation fails for unrelated pre-existing reasons; document those failures
  instead of broadening scope.
~~~

## Rollback

Do not roll back into NVD-listed Git ranges below **2.43.7 / 2.44.4 /
2.45.4 / 2.46.4 / 2.47.3 / 2.48.2 / 2.49.1 / 2.50.1**. Do not flatten
leftover Xcode **26.0** onto Git and do not invent a first_patched
from the 404 global GHAD. If a fixed package or runner image must be
withdrawn, disable untrusted recursive-submodule checkout until
another NVD-excluded Git build is installed.

## Verification - what the reviewer looks for

- Every controlled Git runtime resolves to a fixed version or an explicitly
  backported vendor package.
- CI, devcontainer, Docker, and agent checkout paths do not recursively fetch
  untrusted submodules by default.
- First-party `.gitmodules` policy rejects control characters, path traversal,
  local remotes, unexpected symlinks, and unapproved submodule owners.
- Untrusted repository analysis runs without hooks, write-capable credentials,
  broad host mounts, or privileged network access.
- PR notes identify external runtime owners and operator actions when the
  repository cannot directly patch a runner image.

## Output contract

- Reviewer-ready PR upgrading every controlled Git runtime or documenting the
  external owner and required fixed release line.
- Untrusted checkout defaults that disable recursive submodules, empty hooks,
  write-capable credentials, broad host mounts, and privileged network access.
- Safe regression checks for Git versions, recursive-submodule policy,
  `.gitmodules` control characters/path traversal/local remotes, and secret-safe
  checkout logs.
- `TRIAGE.md` when Git runtime, runner image, repository-intake workflow, or
  credential cleanup ownership is outside this repository.

## Watch for

- Updating a Dockerfile while GitHub Actions, Codespaces, devcontainers, or
  release workers still use an older platform-provided Git binary.
- Treating `actions/checkout` `submodules: recursive` as safe for pull requests
  or issue-driven agent tasks from untrusted sources.
- Auditing `.gitmodules` with a vulnerable Git binary before upgrading the
  runtime.
- Leaving SSH agents, deploy keys, package tokens, cloud credentials, or Docker
  sockets available during source intake from external repositories.
- Relying on a generic SCA scan that checks application dependencies but never
  checks the system Git binary used by CI and agent workers.

## Related recipes

- [Search the CVE Database for CVE-2026-10796](/cve-database/?q=CVE-2026-10796#cve-catalog)
- [Source code supply-chain build integrity audit]({{< relref "/recipes/general/source-code-supply-chain-build-integrity-audit" >}})
- [CVE intelligence intake gate]({{< relref "/recipes/general/cve-intelligence-intake-gate" >}})

## References

- Git advisory: <https://github.com/git/git/security/advisories/GHSA-vwqx-4fm8-6qc9>
- NVD: <https://nvd.nist.gov/vuln/detail/CVE-2025-48384>
- CISA KEV entry: <https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-48384>
- Git release v2.50.1: <https://github.com/git/git/releases/tag/v2.50.1>

description: CVE-2025-48384 leftover. Live GHAD 404. NVD CPE excludes 2.43.7 / 2.44.4 / 2.45.4 / 2.46.4 / 2.47.3 / 2.48.2 / 2.49.1 / 2.50.1.

maturity: stable

model: GPT 5.5 Extra High reasoning

title: CVE-2025-48384: Git Submodule RCE Remediation

vendor: git-scm

part: o

vendor: debian

product: xcode

vendor: apple

quality: curated

recipe_kind: markdown-override

summary: Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When reading a config value, Git strips any trailing carriage return and line feed (CRLF). When writing a config entry, values with a trailing CR are not quoted, causing the CR to be lost when the config is later read. When initializing a submodule, if the submodule path contains a trailing CR, the altered path is read resulting in the submodule being checked out to an incorrect location. If a symlink exists that points the altered path to the submodule hooks directory, and the submodule contains an executable post-checkout hook, the script may be unintentionally executed after checkout. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

title: Git Link Following Vulnerability


summary: Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. When cloning a repository Git knows to optionally fetch a bundle advertised by the remote server, which allows the server-side to offload parts of the clone to a CDN. The Git client does not perform sufficient validation of the advertised bundles, which allows the remote side to perform protocol injection. This protocol injection can cause the client to write the fetched bundle to a location controlled by the adversary. The fetched content is fully controlled by the server, which can in the worst case lead to arbitrary code execution. The use of bundle URIs is not enabled by default and can be controlled by the bundle.heuristic config option. Some cases of the vulnerability require that the adversary is in control of where a repository will be cloned to. This either requires social engineering or a recursive clone with submodules. These cases can thus be avoided by disabling recursive clones. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

title: Git security vulnerability


summary: Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals. The wincred credential helper uses a static buffer (target) as a unique key for storing and comparing against internal storage. This credential helper does not properly bounds check the available space remaining in the buffer before appending to it with wcsncat(), leading to potential buffer overflows. This vulnerability is fixed in v2.43.7, v2.44.4, v2.45.4, v2.46.4, v2.47.3, v2.48.2, v2.49.1, and v2.50.1.

title: Git security vulnerability


product: tar-fs

vendor: mafintosh

summary: tar-fs provides filesystem bindings for tar-stream. Versions prior to 3.0.9, 2.1.3, and 1.16.5 have an issue where an extract can write outside the specified dir with a specific tarball. This has been patched in versions 3.0.9, 2.1.3, and 1.16.5. As a workaround, use the ignore option to ignore non files/directories.


product: freescout

vendor: freescout-help-desk

vendor: freescout

summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.178, the application performs insufficient validation of user-supplied data, which is used as arguments to string formatting functions. As a result, an attacker can pass a string containing special symbols (\r, \n, \t)to the application. This issue has been patched in version 1.8.178.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.178, FreeScout is vulnerable to deserialization of untrusted data due to insufficient validation. Through the set function, a string with a serialized object can be passed, and when getting an option through the get method, deserialization will occur, which will allow arbitrary code execution This issue has been patched in version 1.8.178.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.178, FreeScout is vulnerable to code injection due to insufficient validation of user input in the php_path parameter. The backticks characters are not removed, as well as tabulation is not removed. When checking user input, the file_exists function is also called to check for the presence of such a file (folder) in the file system. A user with the administrator role can create a translation for the language, which will create a folder in the file system. Further in tools.php, the user can specify the path to this folder as php_path, which will lead to the execution of code in backticks. This issue has been patched in version 1.8.178.


product: YouTrack

vendor: JetBrains

version_type: semver

product: youtrack

vendor: jetbrains

summary: In JetBrains YouTrack before 2025.1.76253 deletion of issues was possible due to missing permission checks in API


product: Apache IoTDB

vendor: Apache Software Foundation

product: iotdb

vendor: apache

status: Modified

summary: A vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.3.3 through 1.3.4, from 2.0.1-beta through 2.0.4. Users are recommended to upgrade to version 2.0.5, which fixes the issue.

title: A vulnerability in Apache IoTDB


product: G4 PDU

vendor: Eaton

summary: The server identity check mechanism for firmware upgrade performed via command shell is insecurely implemented potentially allowing an attacker to perform a Man-in-the-middle attack. This security issue has been fixed in the latest firmware version of Eaton G4 PDU which is available on the Eaton download center.

title: Eaton G4 Pdu security vulnerability


summary: An attacker with authenticated and privileged access could modify the contents of a non-sensitive file by traversing the path in the limited shell of the CLI. This security issue has been fixed in the latest version which is available on the Eaton download center.

title: Eaton G4 Pdu security vulnerability


product: NMC G2

summary: An attacker with authenticated and privileged access could modify the contents of a non-sensitive file by traversing the path in the limited shell of the CLI. This security issue has been fixed in the latest version of NMC G2 which is available on the Eaton download center.

title: Eaton Nmc G2 security vulnerability


product: Eaton Brightlayer Software Suite (BLSS)

summary: Arbitrary code execution is possible due to improper validation of the file upload functionality in Eaton BLSS. This security issue has been fixed in the latest script patch latest version of of Eaton BLSS (7.3.0.SCP004).


summary: The privileged user could log in without sufficient credentials after enabling an application protocol. This security issue has been fixed in the latest script patch latest version of of Eaton BLSS (7.3.0.SCP004).


default_status: affected

product: cPH2 / cPP2 charging stations

vendor: eCharge Hardy Barth

summary: The `/etc/passwd` and `/etc/shadow` files reveal hard-coded password hashes for the operating system "root" user. The credentials are shipped with the update files. There is no option for deleting or changing their passwords for an enduser. An attacker can use the credentials to log into the device. Authentication can be performed via SSH backdoor or likely via physical access (UART shell).


summary: There are several scripts in the web interface that are accessible via undocumented hard-coded credentials. The scripts provide access to additional administrative/debug functionality and are likely intended for debugging during development and provides an additional attack surface.


summary: A USB backdoor feature can be triggered by attaching a USB drive that contains specially crafted "salia.ini" files. The .ini file can contain several "commands" that could be exploited by an attacker to export or modify the device configuration, enable an SSH backdoor or perform other administrative actions. Ultimately, this backdoor also allows arbitrary execution of OS commands.


archetype: generic

summary: An OpenSSH daemon listens on TCP port 22. There is a hard-coded entry in the "/etc/shadow" file in the firmware image for the "root" user. However, in the default SSH configuration the "PermitRootLogin" is disabled, preventing the root user from logging in via SSH. This configuration can be bypassed/changed by an attacker through multiple paths though.


summary: The certificate and private key used for providing transport layer security for connections to the web interface (TCP port 443) is hard-coded in the firmware and are shipped with the update files. An attacker can use the private key to perform man-in-the-middle attacks against users of the admin interface. The files are located in /etc/ssl (e.g. salia.local.crt, salia.local.key and salia.local.pem). There is no option to upload/configure custom TLS certificates.

title: Echarge Hardy Barth Cph2 / Cpp2 Charging Stations security vulnerability


product: FortiAnalyzer

vendor: Fortinet

product: FortiAnalyzer Cloud

product: FortiManager

product: FortiManager Cloud

product: fortimanager

vendor: fortinet

product: fortianalyzer

summary: A hidden functionality vulnerability in Fortinet FortiAnalyzer 7.6.0 through 7.6.3, FortiAnalyzer 7.4.0 through 7.4.7, FortiAnalyzer 7.2.0 through 7.2.10, FortiAnalyzer 7.0.0 through 7.0.14, FortiAnalyzer 6.4 all versions, FortiAnalyzer Cloud 7.6.2, FortiAnalyzer Cloud 7.4.1 through 7.4.7, FortiAnalyzer Cloud 7.2.1 through 7.2.10, FortiAnalyzer Cloud 7.0.1 through 7.0.14, FortiAnalyzer Cloud 6.4 all versions, FortiManager 7.6.0 through 7.6.3, FortiManager 7.4.0 through 7.4.7, FortiManager 7.2.0 through 7.2.10, FortiManager 7.0.0 through 7.0.14, FortiManager 6.4 all versions, FortiManager Cloud 7.6.2 through 7.6.3, FortiManager Cloud 7.4.1 through 7.4.7, FortiManager Cloud 7.2.1 through 7.2.10, FortiManager Cloud 7.0.1 through 7.0.14, FortiManager Cloud 6.4 all versions may allow a remote authenticated read-only admin with CLI access to escalate their privilege via use of a hidden command.

title: Fortinet Fortimanager security vulnerability


product: Command Centre Server

vendor: Gallagher

summary: Cleartext Storage of Sensitive Information (CWE-312) in the Gallagher Morpho integration could allow an authenticated user with access to the Command Centre Server to export a specific signing key while in use allowing them to deploy a compromised or counterfeit device on that site. This issue affects Command Centre Server: 9.20 prior to vEL9.20.2819 (MR4), 9.10 prior to vEL9.10.3672 (MR7), 9.00 prior to vEL9.00.3831 (MR8), all versions of 8.90 and prior.

title: Gallagher Command Centre Server security vulnerability


product: Grassroot DICOM

vendor: Grassroot DICOM

vendor: malaterre

summary: An out-of-bounds read vulnerability exists in the RLECodec::DecodeByStreams functionality of Grassroot DICOM 3.024. A specially crafted DICOM file can lead to leaking heap data. An attacker can provide a malicious file to trigger this vulnerability.


summary: Uncaught Exception (CWE-248) in the Command Centre Server allows an Authorized and Privileged Operator to crash the Command Centre Server at will. This issue affects Command Centre Server: 9.30 prior to vEL9.30.2482 (MR2), 9.20 prior to vEL9.20.2819 (MR4), 9.10 prior to vEL9.10.3672 (MR7), 9.00 prior to vEL9.00.3831 (MR8), all versions of 8.90 and prior.


product: Apache Thrift

product: Cryostat 4 on RHEL 9

vendor: Red Hat

version_type: rpm

product: Red Hat Advanced Cluster Management for Kubernetes 2.14

product: Red Hat Advanced Cluster Management for Kubernetes 2.15

product: Red Hat Advanced Cluster Management for Kubernetes 2.16

product: Red Hat OpenShift distributed tracing 3.10.1

product: Red Hat AI Inference Server

product: Red Hat OpenShift Container Platform 4

product: Red Hat OpenShift distributed tracing 3

description: CVE-2025-48431 is Apache Thrift c_glib free mismatch. NVD names 0.23.0. Public GHAD lists the GHSA with empty vulns.

maturity: development

title: CVE-2025-48431: Apache Thrift leftover dump, NVD floor 0.23.0

product: thrift

recipe_kind: markdown-draft

summary: Mismatched Memory Management Routines vulnerability in Apache Thrift c_glib language bindings. This issue affects Apache Thrift: before 0.23.0. Users are recommended to upgrade to version 0.23.0, which fixes the issue. Description: Specially crafted requests can crash an c_glib-based Thrift server with a clean but fatal "free(): invalid pointer" error message.


default_status: unknown

product: Django

vendor: djangoproject

product: django

vendor: debian

summary: An issue was discovered in Django 5.2 before 5.2.3, 5.1 before 5.1.11, and 4.2 before 4.2.23. Internal HTTP response logging does not escape request.path, which allows remote attackers to potentially manipulate log output via crafted URLs. This may lead to log injection or forgery when logs are viewed in terminals or processed by external systems.


product: Trend Micro Password Manager

vendor: Trend Micro, Inc.

vendor: trendmicro

summary: Trend Micro Password Manager (Consumer) version 5.0.0.1266 and below is vulnerable to a Link Following Local Privilege Escalation Vulnerability that could allow a local attacker to leverage this vulnerability to delete files in the context of an administrator when the administrator installs Trend Micro Password Manager.

title: Trendmicro Password Manager security vulnerability


product: Quick Node Block

vendor: Drupal

summary: Missing Authorization vulnerability in Drupal Quick Node Block allows Forceful Browsing.This issue affects Quick Node Block: from 0.0.0 before 2.0.0.

title: Quick Node Block Project Quick Node Block security vulnerability


product: Commerce Eurobank (Redirect)

summary: Incorrect Authorization vulnerability in Drupal Commerce Eurobank (Redirect) allows Functionality Misuse.This issue affects Commerce Eurobank (Redirect): from 0.0.0 before 2.1.1.

title: Commerce Eurobank (Redirect) Project Commerce Eurobank (Redirect) security vulnerability


product: Commerce Alphabank Redirect

summary: Incorrect Authorization vulnerability in Drupal Commerce Alphabank Redirect allows Functionality Misuse.This issue affects Commerce Alphabank Redirect: from 0.0.0 before 1.0.3.

title: Commerce Alphabank Redirect Project Commerce Alphabank Redirect security vulnerability


product: Lightgallery

product: lightgallery

summary: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Drupal Lightgallery allows Cross-Site Scripting (XSS).This issue affects Lightgallery: from 0.0.0 before 1.6.0.

title: Lightgallery Project Lightgallery security vulnerability


product: Admin Audit Trail

summary: Allocation of Resources Without Limits or Throttling vulnerability in Drupal Admin Audit Trail allows Excessive Allocation.This issue affects Admin Audit Trail: from 0.0.0 before 1.0.5.

title: Admin Audit Trail Project Admin Audit Trail security vulnerability


product: Apache IoTDB

product: iotdb

summary: Deserialization of Untrusted Data vulnerability in Apache IoTDB. This issue affects Apache IoTDB: from 1.0.0 before 2.0.5. Users are recommended to upgrade to version 2.0.5, which fixes the issue.


product: Advantech Wireless Sensing and Equipment (WISE)

vendor: Advantech

ecosystem: operating-system

vendor: advantech

summary: Successful exploitation of the vulnerability could allow an unauthenticated attacker to conduct brute force guessing and account takeover as the session cookies are predictable, potentially allowing the attackers to gain root, admin or user access and reset passwords.

title: Advantech Wise-4060Lan Firmware security vulnerability


summary: Successful exploitation of the vulnerability could allow an attacker to consume all available session slots and block other users from logging in, thereby preventing legitimate users from gaining access to the product.


product: DuckDuckGo Browser

vendor: DuckDuckGo

version: 5.246.0 and below

summary: Successful exploitation of the vulnerability could allow an unauthenticated attacker to gain access to a victim’s Sync account data such as account credentials and email protection information.

title: Duckduckgo Duckduckgo Browser security vulnerability


summary: Successful exploitation of the vulnerability could allow an unauthenticated, remote attacker to send Modbus TCP packets to manipulate Digital Outputs, potentially allowing remote control of relay channel which may lead to operational or safety risks.


summary: Successful exploitation of the vulnerability could allow an attacker to cause repeated reboots, potentially leading to remote denial-of-service and system unavailability.

title: Advantech Wise-4010Lan Firmware security vulnerability


summary: Successful exploitation of the vulnerability could allow an attacker that has physical access to interface with JTAG to inject or modify firmware.


summary: Successful exploitation of the vulnerability could allow an unauthenticated attacker to upload firmware through a public update page, potentially leading to backdoor installation or privilege escalation.


summary: Successful exploitation of the stored cross-site scripting vulnerability could allow an attacker to inject malicious scripts into device fields and executed in other users’ browser, potentially leading to session hijacking, defacement, credential theft, or privilege escalation.


product: freescout

vendor: freescout-help-desk

vendor: freescout

summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.179, the application does not check or performs insufficient checking of files uploaded to the application. This allows files to be uploaded with the phtml and phar extensions, which can lead to remote code execution if the Apache web server is used. This issue has been patched in version 1.8.179.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.179, there is no check to ensure that the user is disabling notifications for the mailbox to which they already have access. Moreover, the code explicitly implements functionality that if the user does not have access to the mailbox, then after disabling (enabling) notifications for this mailbox, the user will gain access to it. This issue has been patched in version 1.8.179.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.179, when creating a conversation from a message in another conversation, there is no check to ensure that the user has the ability to view this message. Thus, the user can view arbitrary messages from other mailboxes or from other conversations to which they do not have access (access restriction to conversations is implemented by the show_only_assigned_conversations setting, which is also not checked). This issue has been patched in version 1.8.179.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the application incorrectly checks user access rights for conversations. Users with show_only_assigned_conversations enabled can assign themselves to an arbitrary conversation from the mailbox to which they have access, thereby bypassing the restriction on viewing conversations. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the System does not provide a check on which "clients" of the System an authorized user can view and edit, and which ones they cannot. As a result, an authorized user who does not have access to any of the existing mailboxes, as well as to any of the existing conversations, has the ability to view and edit the System's clients. The limitation of client visibility can be implemented by the limit_user_customer_visibility setting, however, in the specified scenarios, there is no check for the presence of this setting. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, when adding and editing user records using the fill() method, there is no check for the absence of the password field in the data coming from the user, which leads to a mass-assignment vulnerability. As a result, a user with the right to edit other users of the system can change their password, and then log in to the system using the set password. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the application's logic requires the user to perform a correct sequence of actions to implement a functional capability, but the application allows access to the functional capability without correctly completing one or more actions in the sequence. The leaves the attributes of Mailbox object able to be changed by the fill method. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, insufficient input validation during user creation has resulted in a mass assignment vulnerability, allowing an attacker to manipulate all fields of the object, which are enumerated in the $fillable array (the User object), when creating a new user. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the laravel-translation-manager package does not correctly validate user input, enabling the deletion of any directory, given sufficient access rights. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, an authorized user with the administrator role or with the privilege User::PERM_EDIT_USERS can create a user, specifying the path to the user's avatar ../.htaccess during creation, and then delete the user's avatar, resulting in the deletion of the file .htaccess in the folder /storage/app/public. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, an attacker with an unactivated email invitation containing invite_hash, can exploit this vulnerability to self-activate their account, despite it being blocked or deleted, by leveraging the invitation link from the email to gain initial access to the account. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, there is a mass assignment vulnerability. The Customer object is updated using the fill() method, which processes fields such as channel and channel_id. However, the fill() method is called with all client-provided data, including unexpected values for channel and channel_id, leading to a mass assignment vulnerability. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the application is vulnerable to Cross-Site Scripting (XSS) attacks due to incorrect input validation and sanitization of user-input data during mail signature sanitization. An attacker can inject arbitrary HTML code, including JavaScript scripts, into the page processed by the user's browser, allowing them to steal sensitive data, hijack user sessions, or conduct other malicious activities. Additionally, if an administrator accesses one of these emails with a modified signature, it could result in a subsequent Cross-Site Request Forgery (CSRF) vulnerability. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.178, the application is vulnerable to Cross-Site Scripting (XSS) attacks due to incorrect input validation and sanitization of user-input data in the conversation POST data body. This issue has been patched in version 1.8.178.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the application is vulnerable to Cross-Site Scripting (XSS) attacks due to incorrect input validation and sanitization of user-input data when an authenticated user updates the profile of an arbitrary customer. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the cross-site scripiting (XSS) vulnerability is caused by the lack of input validation and sanitization in both \Session::flash and __, allowing user input to be executed without proper filtering. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, when creating a translation of a phrase that appears in a flash-message after a completed action, it is possible to inject a payload to exploit XSS vulnerability. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, deleting the file .htaccess allows an attacker to upload an HTML file containing malicious JavaScript code to the server, which can result in a Cross-Site Scripting (XSS) vulnerability. This issue has been patched in version 1.8.180.


summary: FreeScout is a free self-hosted help desk and shared mailbox. Prior to version 1.8.180, the application is vulnerable to Cross-Site Scripting (XSS) attacks due to insufficient data validation and sanitization during data reception. This issue has been patched in version 1.8.180.


product: laravel-rest-api

vendor: Lomkit

summary: Laravel Rest Api is an API generator. Prior to version 2.13.0, a validation bypass vulnerability was discovered where multiple validations defined for the same attribute could be silently overridden. Due to how the framework merged validation rules across multiple contexts (such as index, store, and update actions), malicious actors could exploit this behavior by crafting requests that bypass expected validation rules, potentially injecting unexpected or dangerous parameters into the application. This could lead to unauthorized data being accepted or processed by the API, depending on the context in which the validation was bypassed. This issue has been patched in version 2.13.0.

title: Laravel Rest Api is an API generator


product: GetSimpleCMS-CE

vendor: GetSimpleCMS-CE

vendor: getsimple-ce

summary: GetSimple CMS is a content management system. In versions starting from 3.3.16 to 3.3.21, an authenticated user with access to the Edit component can inject arbitrary PHP into a component file and execute it via a crafted query string, resulting in Remote Code Execution (RCE). This issue is set to be patched in version 3.3.22.


vendor: yiisoft

vendor: yiiframework

summary: The Yii 2 Redis extension provides the redis key-value store support for the Yii framework 2.0. On failing connection, the extension writes commands sequence to logs. Prior to version 2.0.20, AUTH parameters are written in plain text exposing username and password. That might be an issue if attacker has access to logs. Version 2.0.20 fixes the issue.


product: Gokapi

vendor: Forceu

product: gokapi

vendor: forceu

summary: Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. When using end-to-end encryption, a stored cross-site scripting vulnerability can be exploited by uploading a file with JavaScript code embedded in the filename. After upload and every time someone opens the upload list, the script is then parsed. Prior to version 2.0.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users using a version prior to 2.0.0. If a user is the only authenticated user using Gokapi, they are not affected. This issue has been fixed in v2.0.0. A possible workaround would be to disable end-to-end encryption.


summary: Gokapi is a self-hosted file sharing server with automatic expiration and encryption support. By renaming the friendly name of an API key, an authenticated user could inject JS into the API key overview, which would also be executed when another user clicks on his API tab. Prior to version 2.0.0, there was no user permission system implemented, therefore all authenticated users were already able to see and modify all resources, even if end-to-end encrypted, as the encryption key had to be the same for all users of versions prior to 2.0.0. If a user is the only authenticated user using Gokapi, they are not affected. This issue has been fixed in v2.0.0. A workaround would be to not open the API page if it is possible that another user might have injected code.


product: ValveLink SOLO

vendor: Emerson

less_than: ValveLink 14.0

product: ValveLink DTM

product: ValveLink PRM

product: ValveLink SNAP-ON

version_end_excluding: ValveLink 14.0

summary: Emerson ValveLink products use a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.

title: Emerson Valvelink Solo security vulnerability


product: iroha Board

vendor: iroha Soft Co., Ltd.

version: versions v0.10.12 and earlier

vendor: irohasoft

summary: Cross-site request forgery vulnerability exists in iroha Board versions v0.10.12 and earlier. If a user accesses a specially crafted URL while being logged in to the affected product, arbitrary learning histories may be registered.


vendor: Bloomberg

vendor: bloomberg

summary: A null pointer dereference vulnerability exists in the Distributed Transaction component of Bloomberg Comdb2 8.1 when processing a number of fields used for coordination. A specially crafted protocol buffer message can lead to a denial of service. An attacker can simply connect to a database instance over TCP and send the crafted message to trigger this vulnerability.

title: Bloomberg Comdb2 security vulnerability


product: DocuPrint CP225 w

vendor: FUJIFILM Business Innovation Corp.

version: 01.23.02 and earlier

product: DocuPrint CP228 w

product: DocuPrint CP115 w

version: 01.09.00 and earlier

product: DocuPrint CP118 w

product: DocuPrint CP116 w

product: DocuPrint CP119 w

product: DocuPrint CM225 fw

version: 01.12.02 and earlier

product: DocuPrint CM228 fw

product: DocuPrint CM115 w

version: 01.09.01 and earlier

product: DocuPrint CM118 w

product: Apoes 2150 N

version: 01.00.47 and earlier

product: Apoes 2350 NDA

summary: Out-of-bounds write vulnerability exists in FUJIFILM Business Innovation MFPs. A specially crafted IPP (Internet Printing Protocol) or LPD (Line Printer Daemon) packet may cause a denial-of-service (DoS) condition on an affected MFP. Resetting the MFP is required to recover from the denial-of-service (DoS) condition.


product: BIG-IP Edge Client

product: BIG-IP

summary: A missing file integrity check vulnerability exists on MacOS F5 VPN browser client installer that may allow a local, authenticated attacker with access to the local file system to replace it with a malicious package installer. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

title: F5 Big-Ip Access Policy Manager security vulnerability


product: Nimesa Backup and Recovery

vendor: Nimesa

summary: An OS command injection issue exists in Nimesa Backup and Recovery v2.3 and v2.4. If this vulnerability is exploited, an arbitrary OS commands may be executed on the server where the product is running.


product: AMD μProf

vendor: AMD

product: uprof

vendor: amd

summary: Improper input validation within AMD uprof can allow a local attacker to overwrite MSR registers, potentially resulting in crash or denial of service.

title: Amd Uprof security vulnerability


product: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Renoir")

product: AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R")

product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Picasso")

product: AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Phoenix")

product: AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics (formerly codenamed "Mendocino")

product: AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Dragon Range")

product: AMD Ryzen™ 7000 Series Desktop Processors (formerly codenamed "Raphael"/"Raphael X3D")

product: AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Barcelo R")

product: AMD Ryzen™ AI 300 Series Processors (formerly codenamed "Strix Point")

product: AMD Ryzen™ 8000 Series Desktop Processors (formerly codenamed "Phoenix")

product: AMD Ryzen™ 9000 Series Desktop Processors (formerly codenamed "Granite Ridge")

product: AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Cezanne")

summary: A DLL hijacking vulnerability in the AMD Software Installer could allow an attacker to achieve privilege escalation potentially resulting in arbitrary code execution.

title: Amd Amd Ryzen™ 4000 Series Mobile Processors With Radeon™ Graphics (For… security vulnerability


product: Vitis™ Unified Installer for FPGAs & Adaptive SoCs in Windows

status: Awaiting Analysis

summary: Uncontrolled search paths in Vitis™ Unified installation path on local Windows machines could allow DLL injection into these install paths, potentially resulting in arbitrary code execution.

title: Amd Vitis™ Unified Installer For Fpgas & Adaptive Socs In Windows security vulnerability


product: Kria™ SOM

version: Version TBD

product: Zynq™ UltraScale+™ MPSoCs

product: Zynq™ UltraScale+™ RFSoCs

summary: The security state of the calling processor into Trusted Firmware (TF-A) is not used and could potentially allow non-secure processors access to secure memories, access to crypto operations, and the ability to turn on and off subsystems within the SOC.

title: Amd Kria™ Som security vulnerability


product: AMD Radeon™ PRO V710

version: Contact your AMD Customer Engineering representative

summary: Improper Hardware reset flow logic in the GPU GFX Hardware IP block could allow a privileged attacker in a guest virtual machine to control reset operation potentially causing host or GPU crash or reset resulting in denial of service.

title: Amd Amd Radeon™ Pro V710 security vulnerability


product: AMD μProf

product: uprof

summary: Improper return value within AMD uProf can allow a local attacker to bypass KSLR, potentially resulting in loss of confidentiality or availability.

title: Amd Uprof security vulnerability


summary: Improper input validation within AMD uprof can allow a local attacker to write to an arbitrary physical address, potentially resulting in crash or denial of service.

title: Amd Uprof security vulnerability


product: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Renoir")

product: AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R")

product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Picasso")

product: AMD Ryzen™ 3000 Series Desktop Processors (formerly codenamed "Matisse")

product: AMD Ryzen™ Threadripper™ PRO 3000 WX-Series Processors (formerly codenamed "Castle Peak")

product: AMD Ryzen™ Threadripper™ 3000 Processors (formerly codenamed "Castle Peak")

product: AMD Ryzen™ 9000HX Series Processors

summary: Incorrect default permissions in the installation directory for the AMD general-purpose input/output controller (GPIO) could allow an attacker to achieve privilege escalation resulting in arbitrary code execution.


product: AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Phoenix")

product: AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Hawk Point")

product: AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt")

product: AMD Ryzen™ Z1 Series Processors

product: AMD Ryzen™ Embedded 8000 Series Processors

version: AMD Ryzen™ Chipset Driver 7.06.02.123

summary: Use of uninitialized resource within the AMD Platform Management Framework (PMF) could allow an attacker to read a uninitialized kernel memory resulting in loss of confidentiality or availability.

title: Amd Amd Ryzen™ 7035 Series Processors With Radeon™ Graphics (Formerly C… security vulnerability


product: AMD EPYC™ 9004 Series Processors

product: AMD EPYC™ 7003 Series Processors

version: MilanPI 1.0.0.H

product: AMD EPYC™ 9005 Series Processors

version: TurinPI 1.0.0.6

product: AMD EPYC™ 8004 Series Processors

product: AMD EPYC™ Embedded 7003 Series Processors

version: EmbMilanPI-SP3 v9 1.0.0.C

product: AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Genoa")

version: EmbGenoaPI-SP5 1.0.0.C

product: AMD EPYC™ Embedded 9005 Series Processors

product: AMD EPYC™ Embedded 9004 Series Processors (formerly codenamed "Bergamo")

product: AMD EPYC™ Embedded 8004 Series Processors

summary: Insufficient Granularity of Access Control in SEV firmware can allow a privileged attacker to create a SEV-ES Guest to attack SNP guest, potentially resulting in a loss of confidentiality.

title: Amd Amd Epyc™ 9004 Series Processors security vulnerability


product: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics

version: RenoirPI-FP6 1.0.0.Ed

product: AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ 5000 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ 4000 Series Desktop Processors

product: AMD Ryzen™ 5000 Series Desktop Processors with Radeon™ Graphics

product: AMD Ryzen™ Embedded V2000 Series Processors

summary: Insufficient parameter sanitization in AMD Secure Processor (ASP) Boot Loader could allow an attacker with access to SPIROM upgrade to overwrite the memory, potentially resulting in arbitrary code execution.

title: Amd Amd Ryzen™ 4000 Series Mobile Processors With Radeon™ Graphics security vulnerability


version: No fix planned

product: AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics

product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics

product: AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ 7000 Series Desktop Processors

product: AMD Ryzen™ 3000 Series Desktop Processors

product: AMD Ryzen™ Threadripper™ PRO 3000 WX-Series Processors

product: AMD Ryzen™ Threadripper™ 3000 Processors

product: AMD Ryzen™ 9000HX Series Processors

summary: Insecure default configuration state of DDR5 memory module by AGESA Bootloader Firmware could allow an attacker with local user privilege to abuse the unprotected PMIC interface to create a permanent denial of service condition or affect the integrity of the memory module.


product: AMD EPYC™ 9005 Series Processors

product: AMD EPYC™ Embedded 9005 Series Processors

summary: Insufficient Granularity of Access Control in SEV firmware could allow a privileged user with a malicious hypervisor to create a SEV-ES guest with an ASID in the range meant for SEV-SNP guests potentially resulting in a partial loss of confidentiality.

title: Amd Amd Epyc™ 9005 Series Processors security vulnerability


version: AMD Software: Adrenalin Edition 25.6.1 (25.10.x.y), AMD Software: PRO Edition 25.Q2 (25.10.10)

product: AMD Ryzen™ AI 300 Series Processors

product: AMD Ryzen™ 8000 Series Desktop Processors

product: AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics

product: AMD Ryzen™ Al Max+

product: AMD Ryzen™ Embedded 8000 Series Processors

version: AMD Software: Adrenalin Edition 25.6.1 , AMD Software: PRO Edition 25.Q2 (25.10.10)

product: AMD Radeon™ RX 7000 Series Graphics Products

version: AMD Software: Adrenalin Edition 25.6.1 (25.10.13.01), AMD Software: PRO Edition 25.Q2 (25.10.10)

product: AMD Radeon™ PRO W7000 Series Graphics Products

product: AMD Radeon™ RX 9000 Series Graphics Products

product: AMD Radeon™ PRO V710

summary: Improper input validation in AMD Graphics Driver could allow a local attacker to write out of bounds, potentially resulting in loss of integrity or denial of service.

title: Amd Amd Ryzen™ 7040 Series Mobile Processors With Radeon™ Graphics security vulnerability


product: AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R")

product: AMD Ryzen™ 7040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Phoenix")

product: AMD Ryzen™ 8040 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Hawk Point")

product: AMD Ryzen™ 6000 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt")

summary: An improper input validation vulnerability within the AMD Platform Management Framework (PMF) driver can allow a local attacker to read or write Out-of-Bounds, potentially resulting in privilege escalation


summary: An improper input validation vulnerability within the AMD Platform Management Framework (PMF) driver can allow a local attacker to read Out-of-Bounds potentially resulting in information disclosure or a crash


product: AMD Ryzen™ 4000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Renoir")

version: AMD Ryzen™ Chipset Driver 7.02.13.148

product: AMD Athlon™ 3000 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Picasso")

product: AMD Ryzen™ 7020 Series Processors with Radeon™ Graphics (formerly codenamed "Mendocino")

product: AMD Ryzen™ 7045 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Dragon Range")

product: AMD Ryzen™ 7000 Series Desktop Processors (formerly codenamed "Raphael"/"Raphael X3D")

product: AMD Ryzen™ 3000 Series Desktop Processors (formerly codenamed "Matisse")

product: AMD Ryzen™ Threadripper™ PRO 3000WX Processors (formerly codenamed "Castle Peak")

product: AMD Ryzen™ 7030 Series Mobile Processors with Radeon™ Graphics (formerly codenamed "Barcelo R")

product: AMD Ryzen™ Threadripper™ 3000 Processors (formerly codenamed "Castle Peak")

product: AMD Ryzen™ AI 300 Series Processors (formerly codenamed "Strix Point")

summary: Improper input validation in the AMD Secure Processor (ASP) PCI driver could allow a local attacker to trigger a Use-After-Free (UAF) condition, potentially resulting in a loss of platform integrity or crash.


product: Android

vendor: Google

product: android

vendor: google

summary: In setDisplayName of AssociationRequest.java, there is a possible way for an app to retain CDM association due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In onCreate of SelectAccountActivity.java, there is a possible way to add contacts without permission due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In isSystem of WifiPermissionsUtil.java, there is a possible permission bypass due to a missing permission check. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In disassociate of DisassociationProcessor.java, there is a possible way for an app to continue reading notifications when not associated to a companion device due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In createMultiProfilePagerAdapter of ChooserActivity.java , there is a possible way for an app to launch the ChooserActivity in another profile due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple locations, there is a possible way to leak hidden work profile notifications due to a logic error in the code. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible way to overlay biometrics due to a tapjacking/overlay attack. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In setRingtoneUri of VoicemailNotificationSettingsUtil.java , there is a possible cross user data leak due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible condition that results in OOB accesses due to an incorrect bounds check. This could lead to remote code execution in combination with other bugs, with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In getCallingPackageName of CredentialStorage, there is a possible permission bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In markMediaAsFavorite of MediaProvider.java, there is a possible way to bypass the WRITE_EXTERNAL_STORAGE permission due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

title: Google Android security vulnerability


summary: In multiple locations, there is a possible way to use apps linked from a context menu of a lockscreen app due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In getDefaultCBRPackageName of CellBroadcastHandler.java, there is a possible escalation of privilege due to a logic error in the code. This could lead to local denial of service with System execution privileges needed. User interaction is not needed for exploitation.


summary: In assertSafeToStartCustomActivity of AppRestrictionsFragment.java , there is a possible way to exploit a parcel mismatch resulting in a launch anywhere vulnerability due to unsafe deserialization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In grantAllowlistedPackagePermissions of SettingsSliceProvider.java, there is a possible way for a third party app to modify secure settings due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple locations, there is a possible way to persistently DoS the device due to improper input validation. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In setApplicationHiddenSettingAsUser of PackageManagerService.java, there is a possible way to hide a system critical package due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In SendPacketToPeer of acl_arbiter.cc, there is a possible out of bounds read due to a use after free. This could lead to remote (proximal/adjacent) code execution with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In processTransactInternal of RpcState.cpp, there is a possible local out of memory write due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In onCreate of FaceSettings.java, there is a possible way to remove biometric unlock across user profiles due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of AccountManagerService.java, there is a possible permanent denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


business_risk: No additional source-verified CVE-specific business impact was established.

uncertainty: The Android bulletin identifies updated AOSP versions 13, 14, 15, and 16 but does not state a universal fixed product version applicable to all Android OEM builds.

uncertainty: The September 5, 2025 patch-level remediation is explicitly documented for Google Pixel devices and should not automatically be generalized to non-Pixel Android devices.

uncertainty: The sources do not provide a vendor-independent safe local test for confirming exploitability or patch effectiveness.

product: Runtime

vendor_project: Android

vulnerability_name: Android Runtime Use-After-Free Vulnerability

summary: In multiple locations, there is a possible way to escape chrome sandbox to attack android system_server due to a use after free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible way to read files belonging to other apps due to SQL injection. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In isSystemUid of AccountManagerService.java, there is a possible way for an app to access privileged APIs due to a confused deputy. This could lead to local privilege escalation with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In checkPermissions of SafeActivityOptions.java, there is a possible background activity launch due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible one-time permission bypass due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.


summary: In multiple functions of AppOpsControllerImpl.java, there is a possible way to record audio without displaying the privacy indicator due to a race condition. This could lead to local escalation of privilege with User execution privileges needed. User interaction is needed for exploitation.

title: Google Android security vulnerability


summary: In multiple locations, there is a possible way to record audio via a background app due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In testGrantSlicePermission of SliceManagerTest.java, there is a possible permanent denial of service due to a path traversal error. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible leak of an image across the Android User isolation boundary due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.


summary: In saveGlobalProxyLocked of DevicePolicyManagerService.java, there is a possible way to desync from persistence due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In handlePackagesChanged of DevicePolicyManagerService.java, there is a possible DoS of a device admin due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In handlePackagesChanged of DevicePolicyManagerService.java, there is a possible persistent denial of service due to a logic error in the code. This could lead to local denial of service with no additional execution privileges needed. User interaction is needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of NotificationStation.java, there is a possible cross-profile information disclosure due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple methods of NotificationChannel.java, there is a possible desynchronization from persistence due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.


summary: In multiple functions of BatteryService.java, there is a possible way to hijack implicit intent intended for system app due to Implicit intent hijacking. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of AppOpsService.java, there is a possible add a large amount of app ops due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In AndroidManifest.xml, there is a possible way for an app to monitor motion events due to a confused deputy. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible way to access data displayed on the screen due to side channel information disclosure. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In writeContent of RemotePrintDocument.java, there is a possible information disclosure due to a logic error. This could lead to local information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.


summary: In onNullBinding of RemoteFillService.java, there is a possible background activity launch due to an insecure default value. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible intent filter bypass due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible way to bypass the cross profile intent filter due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible bypass of user profile boundary with a forwarded intent due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible bypass of a file path filter designed to prevent access to sensitive directories due to incorrect unicode normalization. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

title: Google Android security vulnerability


summary: In multiple locations, there is a possible lockscreen bypass due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible permanent denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of PipTaskOrganizer.java, there is a possible way to launch an activity from the background due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of btm_sec.cc, there is a possible way for an attacker to intercept SMS messages due to a logic error in the code. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.


business_risk: High-risk local privilege-escalation vulnerability in Android Framework. A low-privileged local app may bypass permissions to launch activities from the background, potentially gaining elevated access without user interaction. The CVE is listed in CISA's Known Exploited Vulnerabilities Catalog.

claim: The Android December 2025 security bulletin lists CVE-2025-48572 as a high-severity Framework elevation-of-privilege issue affecting updated AOSP versions 13, 14, 15, and 16.

claim: NVD records Google Android 13.0, 14.0, 15.0, and 16.0 as affected configurations.

claim: The vulnerability permits background activity launches through a permissions bypass and can lead to local privilege escalation without user interaction.

kind: exposure

claim: Android security patch levels of 2025-12-01 or later address all issues associated with the 2025-12-01 security patch level; 2025-12-05 or later also includes the previous patch-level fixes.

claim: The Android bulletin specifies checking the device security patch level and identifies 2025-12-01 and 2025-12-05 as the relevant patch-level thresholds.

kind: verification

exposure_conditions: Android versions 13, 14, 15, or 16 are within the affected scope.

exposure_conditions: The device has an Android security patch level earlier than 2025-12-01.

exposure_conditions: Exploitation is local and requires an attacker-controlled process with low privileges; no user interaction is required.

remediation_steps: Apply the device manufacturer's security update providing Android security patch level 2025-12-01 or later.

remediation_steps: Prefer security patch level 2025-12-05 or later where available, since it includes the 2025-12-05 fixes and all previous patch-level fixes.

remediation_steps: If the device cannot receive the applicable security update, follow the vendor's supported mitigation guidance or replace/retire the device when mitigation is unavailable.

remediation_steps: Confirm that the manufacturer update incorporates the Android Framework fix associated with Android bug A-385736540.

status: complete

uncertainty: The Android bulletin identifies the affected AOSP versions and patch-level remediation but does not establish a universal OEM firmware build number for every Android device.

uncertainty: OEM release timing and build identifiers vary by device, carrier, and manufacturer.

uncertainty: The supplied CPE data identifies Android 13.0 through 16.0, while the vendor bulletin describes affected updated AOSP versions as 13, 14, 15, and 16; device-specific applicability should be confirmed with the manufacturer.

verification_steps: Check the device's reported Android security patch level in the system update/security settings and confirm it is 2025-12-01 or later.

verification_steps: For devices claiming the 2025-12-05 level, confirm the reported patch level is 2025-12-05 or newer.

verification_steps: Record the device model, Android release, security patch level, and update-provider release identifier for audit evidence.

verification_steps: Do not treat an Android major-version number alone as proof of remediation; verify the security patch level supplied by the device manufacturer.

product: Framework

vulnerability_name: Android Framework Privilege Escalation Vulnerability

summary: In multiple locations, there is a possible way to launch activities from the background due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In sendCommand of MediaSessionRecord.java, there is a possible way to launch the foreground service while the app is in the background due to FGS while-in-use abuse. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In validateAddingWindowLw of DisplayPolicy.java, there is a possible way for an app to intercept drag-and-drop events due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of CertInstaller.java, there is a possible way to install certificates due to a permissions bypass. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In updateNotificationChannelGroupFromPrivilegedListener of NotificationManagerService.java, there is a possible permanent denial of service due to resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of KeyguardViewMediator.java, there is a possible lockscreen bypass due to a race condition. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of MediaProvider.java, there is a possible way to bypass the WRITE_EXTERNAL_STORAGE permission due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of MediaProvider.java, there is a possible external storage write permission bypass due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In connectInternal of MediaBrowser.java, there is a possible way to access while in use permission while the app is in background due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In VerifyNoOverlapInSessions of apexd.cpp, there is a possible way to block security updates due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple locations, there is a possible way to delete media without the MANAGE_EXTERNAL_STORAGE permission due to an intent redirect. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of BaseBundle.java, there is a possible way to execute arbitrary code due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of NotificationManagerService.java, there is a possible way to bypass the per-package channel limits causing resource exhaustion. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability


summary: In multiple functions of ProfilingService.java, there is a possible persistent denial of service due to improper input validation. This could lead to local denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In onActivityResult of EditFdnContactScreen.java, there is a possible way to leak contacts from the work profile due to a confused deputy. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


title: In multiple functions of ProfilingService.java, there is a possible persistent denial of service due to improper input validation


summary: In startAlwaysOnVpn of Vpn.java, there is a possible way to disable always-on VPN due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.


summary: In multiple functions of HeaderPrivacyIconsController.kt, there is a possible way to grand permissions across user due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.

title: Google Android security vulnerability