Description Summary:
An incorrect authorization flaw in ash_typescript allows unauthorized RPC callers to access sensitive attribute values that should have been restricted by Ash field policies.

Executive Summary:
An authorization bypass vulnerability in the ash_typescript library allows unauthorized users to access restricted data, posing a high risk to sensitive application information.

Vulnerability Details

CVE-ID: CVE-2026-82730

Affected Software: ash-project ash_typescript

Affected Versions: 0.11.0 up to 0.18.0

Vulnerability: The vulnerability exists in the result processing logic of the ash_typescript library, specifically within the normalize_primitive function. Due to improper handling of forbidden field markers, serialized data can leak restricted attribute values to unauthorized callers.

Business Impact

This vulnerability allows an unauthorized attacker to extract sensitive information that the application was intended to protect via field policies. Given the CVSS score of 8.2, this represents a high-severity risk that could lead to significant data exposure, privacy violations, and non-compliance with data protection regulations.

Remediation Plan

Immediate Action: Update the ash_typescript library to version 0.18.0 or later to ensure the proper sanitization of forbidden field markers.

Proactive Monitoring: Review application logs for unusual RPC request patterns or unexpected data retrieval attempts from embedded resources that may indicate attempted exploitation of this flaw.

Compensating Controls: If an immediate update is not feasible, restrict access to public-facing RPC endpoints that utilize the vulnerable normalize_value_for_json function until the patch can be applied.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of September 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is primarily an implementation error in the serialization logic which, while serious, requires specific configurations to trigger.

Analyst Recommendation

The vulnerability presents a clear risk to data confidentiality by circumventing established field-level security policies. Administrators should prioritize updating the ash_typescript dependency to the remediated version, as the flaw is straightforward to trigger via public entry points. Failure to patch may result in the unauthorized disclosure of restricted resource attributes.

Description Summary:
A flaw in the ash_phoenix SubdomainHook allows bypass of tenant-scoped authorization checks because the tenant identifier is incorrectly evaluated as nil during the initial mount process.

Executive Summary:
An incorrect authorization vulnerability in the ash_phoenix library allows authenticated users to potentially bypass tenant-scoped access controls, posing a significant risk to data isolation.

Vulnerability Details

CVE-ID: CVE-2026-82724

Affected Software: ash-project ash_phoenix

Affected Versions: 2.1.26 up to (excluding) 2.3.25

Vulnerability: The vulnerability exists in the SubdomainHook authorization callback, which executes before the tenant assignment is fully processed by the LiveView lifecycle. This results in the authorization logic evaluating a nil tenant, which may cause the application to default to a permissive state for authenticated users.

Business Impact

The failure to properly enforce tenant isolation can lead to unauthorized access to sensitive data belonging to other tenants within a multi-tenant environment. Given the CVSS score of 7.6, this vulnerability is classified as High severity, as it directly compromises the integrity and confidentiality of customer data and undermines the fundamental security architecture of the application.

Remediation Plan

Immediate Action: Update the ash_phoenix library to version 2.3.25 or later to ensure that tenant-scoped authorization checks are correctly synchronized with the LiveView navigation lifecycle.

Proactive Monitoring: Review application logs for unusual access patterns, specifically focusing on cross-tenant requests or unexpected authorization errors following recent deployments.

Compensating Controls: Ensure that secondary authorization checks are implemented at the data access or repository layer, which serves as a fail-safe if the application-level hook is bypassed.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is primarily an implementation error in the hook execution order, which requires an existing authenticated session to trigger.

Analyst Recommendation

This vulnerability represents a significant risk to multi-tenant architectures by weakening core access control mechanisms. Administrators should prioritize upgrading the affected ash_phoenix dependency across all environments immediately to prevent potential data leakage or unauthorized cross-tenant access.

Description Summary:
A resource exhaustion vulnerability in ash_admin allows authenticated users to crash the BEAM virtual machine by flooding LiveView event handlers with unvalidated input.

Executive Summary:
An allocation of resources vulnerability in the ash_admin LiveView component allows authenticated attackers to trigger a denial of service by exhausting the BEAM atom table.

Vulnerability Details

CVE-ID: CVE-2026-82722

Affected Software: ash-project ash_admin

Affected Versions: 0.1.0 up to (excluding) 1.3.1

Vulnerability: The vulnerability exists within the AshAdmin.PageLive and AshAdmin.Components.Resource.Show event handlers, which improperly convert unvalidated client input into atoms. Because atoms are not garbage collected in the BEAM virtual machine, an authenticated user can flood these handlers to exhaust the atom table, forcing the node to abort.

Business Impact

The exploitation of this flaw leads to a complete denial of service for the affected node, resulting in significant system downtime and potential disruption of dependent applications. With a CVSS score of 8.3, the vulnerability is classified as High severity, reflecting the ease of execution and the catastrophic impact on service availability.

Remediation Plan

Immediate Action: Update the ash_admin dependency to version 1.3.1 or later to ensure all user input is properly validated against declared resources and arguments.

Proactive Monitoring: Monitor system logs for unusual spikes in memory usage or repeated node crashes that correlate with access to the ash_admin LiveView endpoints.

Compensating Controls: Restrict access to the ash_admin interface to trusted administrative networks or utilize a Web Application Firewall to filter requests that exhibit patterns consistent with automated atom-generation attacks.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the nature of BEAM atom management, where a single user can trigger a global node shutdown without high administrative privileges.

Analyst Recommendation

Given the ease with which this vulnerability can be leveraged to cause a total service outage, organizations using ash_admin must prioritize updating to version 1.3.1 immediately. The lack of public exploits does not mitigate the risk, as the mechanism for exploitation is well-documented within the security advisory.

Description Summary:
A path traversal vulnerability in ash_admin allows authenticated attackers to write arbitrary files to the server, potentially leading to remote code execution.

Executive Summary:
A path traversal vulnerability in the ash_admin package allows authenticated users to achieve arbitrary file writes, creating a critical risk of remote code execution.

Vulnerability Details

CVE-ID: CVE-2026-82673

Affected Software: ash-project ash_admin

Affected Versions: 0.13.7 up to 1.3.1

Vulnerability: This is a path traversal vulnerability (CWE-22) occurring within the AshAdmin.Components.Resource.Form.consume_file_uploads/1 function. The application fails to sanitize the client provided filename, allowing an authenticated attacker to escape the intended temporary directory and write files to arbitrary locations on the server.

Business Impact

The ability to write arbitrary files to the server provides an attacker with the capability to overwrite critical application assets, configuration files, or system binaries. This level of access typically results in full system compromise, remote code execution, and potential data exfiltration. Given the CVSS score of 8.3, this high severity vulnerability necessitates immediate remediation to prevent unauthorized system control.

Remediation Plan

Immediate Action: Upgrade the ash_admin package to version 1.3.1 or later to implement proper filename sanitization using Path.basename/1.

Proactive Monitoring: Review web server logs for file upload requests containing directory traversal sequences, such as dot-dot-slash patterns, directed at administration endpoints.

Compensating Controls: Implement strict file type validation and rename uploaded files to randomized strings on the server side to neutralize path injection attempts if an immediate update is not feasible.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the direct control it grants over the file system via unsanitized user input.

Analyst Recommendation

The risk posed by this path traversal vulnerability is significant, as it provides a clear path to full system compromise for any authenticated user. Organizations utilizing the ash_admin package should prioritize updating to the patched version immediately. Failure to address this vulnerability allows an attacker to bypass directory restrictions and execute arbitrary commands on the underlying server.

Description Summary:
A vulnerability in ash_ai allows authenticated users to bypass authorization checks, enabling the unauthorized modification or destruction of database records via manipulated tool arguments.

Executive Summary:
An authorization bypass vulnerability in the ash_ai library allows an authenticated caller to modify or destroy arbitrary records, posing a severe risk to data integrity.

Vulnerability Details

CVE-ID: CVE-2026-82564

Affected Software: ash-project ash_ai

Affected Versions: 0.6.0 up to 1.0.0

Vulnerability: This flaw is an Authorization Bypass Through User-Controlled Key (CWE-639) occurring in the AshAi.Tool.Execution module. By supplying crafted predicate expressions instead of literal values as tool arguments, an authenticated attacker can manipulate database queries to target records beyond their authorization scope.

Business Impact

The ability to arbitrarily update or delete database entries represents a critical risk to business operations and data reliability. A successful exploit could lead to unauthorized data destruction or modification, potentially resulting in significant operational downtime and loss of data integrity. With a CVSS score of 7.1, this vulnerability is classified as High severity, necessitating prompt attention to prevent unauthorized state changes in backend systems.

Remediation Plan

Immediate Action: Upgrade the ash_ai library to version 1.0.0 or later, which incorporates the necessary input validation to cast identity values to the correct field types.

Proactive Monitoring: Review application logs for unusual bulk update or destroy operations, specifically monitoring for tool execution patterns that include unexpected predicate structures in arguments.

Compensating Controls: Implement strict input validation or sanitization layers for all tool-configured inputs before they are passed to query execution functions to reject non-scalar inputs.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the ease with which query parameters can be manipulated to bypass authorization, but it requires the attacker to have at least low-level authenticated access to the system.

Analyst Recommendation

Given the potential for unauthorized data destruction, organizations utilizing the ash_ai library must prioritize updating to version 1.0.0. Security teams should verify their dependency trees to identify affected versions and ensure the patch is applied across all environments, as this vulnerability directly facilitates the manipulation of database records by authenticated callers.

Description Summary:
An unauthenticated resource exhaustion vulnerability in ash_graphql allows attackers to bypass query complexity limits, causing unbounded database reads through specifically crafted GraphQL queries.

Executive Summary:
A critical resource exhaustion vulnerability in the ash_graphql library allows unauthenticated attackers to bypass complexity limits and trigger excessive database consumption.

Vulnerability Details

CVE-ID: CVE-2026-81636

Affected Software: ash-project ash_graphql

Affected Versions: 0.16.23 up to (excluding) 1.11.0

Vulnerability: This is an allocation of resources without limits or throttling (CWE-770) issue found in the query complexity calculation logic. An unauthenticated attacker can supply crafted nested Relay connection queries that are incorrectly scored as low complexity, enabling the execution of resource-intensive database operations.

Business Impact

The vulnerability poses a significant risk of denial of service for applications relying on the ash_graphql library. By forcing the database to materialize large datasets, an attacker can consume excessive system resources, leading to severe performance degradation or complete service unavailability. Given the CVSS score of 8.7, this is considered a high-severity issue that directly threatens system stability and availability.

Remediation Plan

Immediate Action: Update the ash_graphql library to version 1.11.0 or later to ensure proper query complexity enforcement for all pagination types.

Proactive Monitoring: Monitor database performance metrics, such as query execution time and CPU load, for spikes following GraphQL request patterns.

Compensating Controls: Implement strict rate limiting at the API gateway or Web Application Firewall (WAF) level to prevent excessive request volumes from unauthenticated sources.

Exploitation Status

Public Exploit Available: Unknown.

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable because it relies on a logical error in how the library calculates the complexity of nested Relay connection queries, which can be easily triggered by any external client.

Analyst Recommendation

Organizations utilizing the ash_graphql library should prioritize upgrading to version 1.11.0 immediately. Because the vulnerability allows unauthenticated access to resource-intensive operations, the potential for service disruption is substantial. Administrators should verify their dependency versions and apply the patch as part of their next maintenance window to mitigate the risk of denial of service attacks.

Description Summary:
A flaw in ash_ai allows unauthenticated attackers to bypass DNS-rebinding protections via malicious web pages, leading to unauthorized cross-site requests to a user's local MCP server.

Executive Summary:
A vulnerability in the ash_ai package allows attackers to bypass origin validation, enabling unauthorized cross-site requests to local MCP servers and posing a high risk to user data integrity.

Vulnerability Details

CVE-ID: CVE-2026-81315

Affected Software: ash-project ash_ai

Affected Versions: 0.8.0 up to 1.0.0

Vulnerability: The vulnerability, categorized as an Origin Validation Error (CWE-346), exists within the AshAi.Mcp.Server module. Attackers can manipulate the Host and X-Forwarded-Proto headers to deceive the server into accepting unauthorized origins, effectively bypassing security checks without requiring any authentication.

Business Impact

This vulnerability carries a CVSS score of 7.4, indicating a high level of risk. Successful exploitation permits an attacker to perform actions on the local MCP server on behalf of the user, which can lead to unauthorized data access, modification, or the execution of unintended commands. Such compromises can result in significant operational disruption and the loss of sensitive information processed by the local AI integration.

Remediation Plan

Immediate Action: Update the ash_ai package to version 1.0.0 or later to ensure the server correctly restricts origins to localhost by default.

Proactive Monitoring: Review web server access logs for anomalous requests containing suspicious Host headers or unexpected X-Forwarded-Proto values.

Compensating Controls: Implement strict Network Access Control Lists or ensure the local MCP server is not exposed to untrusted web content to prevent DNS-rebinding attacks.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw relies on browser-based DNS-rebinding techniques, which are inherently opportunistic and require the user to visit a malicious site while the local server is active.

Analyst Recommendation

Given the potential for unauthorized access to local resources, organizations should prioritize updating the ash_ai package immediately. The transition to a whitelist-only origin policy in version 1.0.0 is a critical security improvement that effectively mitigates this attack vector. Ensure all development and production environments are patched to prevent potential exploitation.

Description Summary:
An incorrect authorization flaw in ash_graphql allows authenticated users to access data belonging to other tenants via GraphQL subscriptions due to improper in-memory policy evaluation.

Executive Summary:
A critical authorization bypass vulnerability in ash_graphql allows authenticated subscribers to access unauthorized cross-tenant data, posing a significant risk to multi-tenant data privacy.

Vulnerability Details

CVE-ID: CVE-2026-80223

Affected Software: ash-project ash_graphql

Affected Versions: 1.4.0 up to (excluding) 1.11.0

Vulnerability: The vulnerability exists in the subscription resolver, which performs authorization checks in-memory without applying necessary tenant-level guards. Because the evaluation logic fails to enforce tenant isolation during the subscription process, an authenticated user can receive data records belonging to a different tenant.

Business Impact

Successful exploitation of this vulnerability results in unauthorized access to sensitive data across tenant boundaries, which directly violates data privacy and compliance requirements. With a CVSS score of 7.1, this high-severity flaw could lead to significant data exposure and loss of customer trust in multi-tenant environments.

Remediation Plan

Immediate Action: Upgrade the ash_graphql package to version 1.11.0 or later to ensure that proper tenant guards are applied to all subscription resolvers.

Proactive Monitoring: Review application logs for unusual GraphQL subscription traffic or patterns where users are accessing data that appears outside their assigned tenant scope.

Compensating Controls: If immediate patching is not feasible, restrict access to the GraphQL subscription endpoints or implement secondary application-level filtering to validate tenant ownership before data is transmitted to the client.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherent to the logic of the notification payload processing within the library and requires an authenticated session to trigger.

Analyst Recommendation

The severity of this authorization flaw necessitates immediate attention, particularly for providers of multi-tenant software services. Organizations using ash_graphql must prioritize upgrading to the fixed version to prevent potential data leakage between tenants, as the current implementation fails to enforce mandatory access control boundaries.

Description Summary:
An unchecked return value in ash_postgres allows authenticated users to perform tenant name collisions, potentially leading to unauthorized cross-tenant data access.

Executive Summary:
A critical vulnerability in ash_postgres allows an authenticated user to gain unauthorized access to data belonging to other tenants through a tenant rename collision.

Vulnerability Details

CVE-ID: CVE-2026-78699

Affected Software: ash-project ash_postgres

Affected Versions: 0.25.0 up to 2.13.0

Vulnerability: This is an unchecked return value vulnerability (CWE-252) occurring in the AshPostgres.MultiTenancy.rename_tenant function, where database errors are ignored, allowing an authenticated user to manipulate schema associations.

Business Impact

Successful exploitation allows an authenticated user to bypass tenant isolation boundaries, resulting in unauthorized access to sensitive data belonging to other tenants. With a CVSS score of 7.2, this vulnerability represents a significant risk to data confidentiality and integrity, potentially leading to severe regulatory compliance issues and loss of customer trust.

Remediation Plan

Immediate Action: Upgrade ash_postgres to version 2.13.0 or later immediately to incorporate the necessary error handling for tenant rename operations.

Proactive Monitoring: Review application and database logs for failed or unusual tenant rename operations that might indicate an attempt to trigger schema collisions.

Compensating Controls: Restrict access to tenant management functions to highly privileged users only, and implement application-level validation to prevent naming collisions before database operations occur.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw exists because the software fails to verify the success of a database schema rename operation, allowing the application to proceed as if the operation succeeded even when it fails.

Analyst Recommendation

The risk posed by this vulnerability is high due to the potential for cross-tenant data exposure. Security teams should prioritize updating the ash_postgres package to the patched version 2.13.0 across all environments to ensure proper validation of database state changes and maintain strict tenant isolation.

Description Summary:
An unauthenticated code injection vulnerability in ash_ai allows remote attackers to execute arbitrary Elixir code by injecting malicious EEx templates into prompt actions.

Executive Summary:
The ash_ai library is vulnerable to unauthenticated remote code execution, posing a critical risk to server integrity and data confidentiality.

Vulnerability Details

CVE-ID: CVE-2026-77956

Affected Software: ash-project ash_ai

Affected Versions: 0.1.0 up to (excluding) 1.0.0

Vulnerability: This vulnerability involves improper control of code generation (CWE-94) where the AshAi.Actions.Prompt module improperly evaluates user-supplied prompt content using EEx.eval_string/2. An unauthenticated remote attacker can inject arbitrary Elixir code, such as system commands, into prompt arguments, which the server then executes during template compilation.

Business Impact

A successful exploit grants an attacker full remote code execution capabilities on the host server. Given the CVSS score of 10.0, this represents the highest level of severity, potentially leading to total system compromise, unauthorized access to sensitive data, and complete operational disruption.

Remediation Plan

Immediate Action: Upgrade the ash_ai package to version 1.0.0 or later to ensure prompt content is no longer evaluated as executable EEx templates.

Proactive Monitoring: Review server logs for suspicious input patterns directed at prompt actions, specifically looking for EEx syntax or unauthorized system calls.

Compensating Controls: Implement strict input validation or sanitization layers at the application gateway to inspect prompt arguments for embedded code structures if immediate patching is not feasible.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of Aug 30, 2026, there is no public information indicating active exploitation or a published proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the direct execution of attacker-controlled strings by the server interpreter.

Analyst Recommendation

This vulnerability is critical and requires immediate attention to prevent unauthorized remote access. Organizations utilizing the ash_ai library must prioritize updating to the patched version, as the current implementation allows trivial execution of arbitrary code by any remote client.

Description Summary:
An unauthenticated resource exhaustion vulnerability in ash_typescript allows attackers to crash the BEAM virtual machine by flooding the atom table with arbitrary input.

Executive Summary:
A critical resource exhaustion vulnerability in the ash_typescript library allows unauthenticated remote attackers to trigger a denial of service by causing the BEAM virtual machine to crash.

Vulnerability Details

CVE-ID: CVE-2026-77856

Affected Software: Ash Project ash_typescript

Affected Versions: 0.11.0 to 0.17.9

Vulnerability: The flaw exists in the resolve_typed_struct_field/2 function, which incorrectly uses String.to_atom/1 on client-supplied data before validating field existence. Because atoms in the BEAM environment are not garbage collected, an unauthenticated attacker can force the creation of infinite permanent atoms until the node reaches its limit and aborts.

Business Impact

This vulnerability poses a significant risk to service availability, as it enables a trivial denial of service attack that does not require authentication. With a CVSS score of 8.2, the impact is high because a successful exploit results in a total crash of the affected application node, leading to potential business disruption and loss of service uptime for end users.

Remediation Plan

Immediate Action: Update the ash_typescript dependency to version 0.18.0 or later, which includes the necessary field existence checks to prevent unauthorized atom creation.

Proactive Monitoring: Monitor application logs for high volumes of unexpected or malformed RPC requests, and track BEAM atom table usage metrics to detect potential exhaustion attempts.

Compensating Controls: Implement rate limiting on all public-facing endpoints that process typed struct fields, and deploy a Web Application Firewall to filter out suspicious or excessively large payloads.

Exploitation Status

Public Exploit Available: No

Analyst Notes: As of September 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the nature of the BEAM atom table, which makes the application highly susceptible to memory exhaustion if input is not strictly validated.

Analyst Recommendation

Given the ease with which an unauthenticated attacker can crash the entire node, this vulnerability should be prioritized for immediate remediation. Organizations utilizing the ash_typescript library must update to the patched version as soon as possible to prevent potential service instability and denial of service incidents.

Description Summary:
A stored cross-site scripting (XSS) vulnerability in ash_admin allows lower-privileged users to execute malicious scripts in an administrator's browser session via crafted record labels.

Executive Summary:
The ash_admin library is vulnerable to stored cross-site scripting, which allows an authenticated attacker to execute arbitrary JavaScript in the context of an administrator's session.

Vulnerability Details

CVE-ID: CVE-2026-77850

Affected Software: ash-project ash_admin

Affected Versions: 0.13.0 up to 1.3.1

Vulnerability: The vulnerability exists due to improper neutralization of input in the AshAdmin.Components.Resource.RelationshipField and ManagedRelationshipSelectField components. An authenticated user can inject malicious payloads into database content that is subsequently rendered without output escaping, triggering script execution when an administrator interacts with the affected UI elements.

Business Impact

Successful exploitation grants an attacker the full privileges of the targeted administrator within the ash_admin interface. This could lead to unauthorized configuration changes, data exfiltration, or complete takeover of the administrative dashboard. With a CVSS score of 8.4, this high-severity flaw poses a significant risk to organizational integrity and data confidentiality.

Remediation Plan

Immediate Action: Upgrade the ash_admin package to version 1.3.1 or later to ensure proper HTML escaping of label fields.

Proactive Monitoring: Review application access logs for anomalous requests, particularly those involving the creation or modification of records that appear in typeahead or relationship selection components.

Compensating Controls: Deploy a Content Security Policy (CSP) to restrict the execution of unauthorized inline scripts, which may mitigate the impact of this XSS vulnerability if immediate patching is not feasible.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the combination of stored input and administrative context, making it a high-priority target for testing.

Analyst Recommendation

Given the high CVSS score and the potential for full administrative compromise, organizations using ash_admin must prioritize this update. Verify that all instances are running version 1.3.1 or later to prevent malicious actors from leveraging stored XSS to hijack high-privileged sessions.

Description Summary:
The ash_ai library improperly handles embedding provider errors, leading to the exposure of sensitive credentials and request state in user-facing validation messages.

Executive Summary:
A high-severity information disclosure vulnerability in ash_ai allows authenticated users to capture sensitive API credentials via crafted error messages.

Vulnerability Details

CVE-ID: CVE-2026-75760

Affected Software: ash-project ash_ai

Affected Versions: 0.1.0 up to (excluding) 1.0.0

Vulnerability: This vulnerability involves the generation of error messages containing sensitive information (CWE-209). By submitting malformed or oversized content that triggers an embedding provider failure, an authenticated user can force the application to return raw error terms, including outbound Authorization headers and API keys, directly to the caller.

Business Impact

The exposure of API keys and provider request details poses a significant risk to organizational security, as it grants attackers the potential to hijack third-party AI services or perform unauthorized actions on behalf of the application. With a CVSS score of 7.1, this vulnerability is considered High, as it enables the compromise of sensitive authentication material that could lead to further downstream attacks or service abuse.

Remediation Plan

Immediate Action: Update the ash_ai dependency to version 1.0.0 or later, which implements sanitized error logging to prevent the leakage of raw provider error terms.

Proactive Monitoring: Review application logs for unusual spikes in validation errors or repeated attempts to submit malformed input that triggers embedding processes.

Compensating Controls: If immediate patching is not feasible, restrict access to the affected endpoints and ensure that API keys used by the embedding service have the minimum necessary scope and are regularly rotated.

Exploitation Status

Public Exploit Available: Unknown

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently exploitable by any authenticated user who can reach the vectorization endpoint.

Analyst Recommendation

Given the ease of exploitation and the severity of credential exposure, organizations should prioritize the update to version 1.0.0. Failure to patch allows authenticated users to potentially exfiltrate production API credentials, creating a substantial risk to both the integrity of the application and the security of third-party AI integrations.

Description Summary:
A cookie validation flaw in ash_admin allows an attacker controlling a sibling subdomain to hijack an administrator session by injecting shadowing cookies.

Executive Summary:
The ash_admin library is vulnerable to a critical session hijacking flaw that permits attackers to impersonate administrators or alter authorization modes by exploiting improper cookie name matching.

Vulnerability Details

CVE-ID: CVE-2026-75757

Affected Software: ash-project ash_admin

Affected Versions: 0.9.1 up to (excluding) 1.3.1

Vulnerability: This is a reliance on cookies without validation and integrity checking (CWE-565). The client-side JavaScript uses an unanchored regular expression to parse cookies, allowing an attacker to override sensitive session state via a malicious cookie set on a shared registrable domain.

Business Impact

The vulnerability carries a CVSS score of 8.3, indicating a high level of risk. A successful exploit allows unauthorized actors to rebind an administrator session to a different tenant or actor, potentially leading to full administrative account takeover, unauthorized data access, and the bypass of critical security controls within the application.

Remediation Plan

Immediate Action: Update the ash_admin dependency to version 1.3.1 or later, which implements exact equality matching for cookie names to prevent shadowing.

Proactive Monitoring: Review application logs for unusual session activity or authentication requests originating from unexpected subdomains.

Compensating Controls: Implement strict Content Security Policy (CSP) headers and ensure that cookies are scoped to the narrowest possible domain, preventing cross-subdomain cookie leakage.

Exploitation Status

Public Exploit Available: No (exploit_available: false)

Analyst Notes: As of August 31, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the ease with which a compromised sibling domain can influence the primary application state.

Analyst Recommendation

Given the potential for complete administrative session compromise, organizations utilizing ash_admin must prioritize this update. The ease of exploitation via sibling domain control necessitates immediate patching to ensure the integrity of the administration interface and its associated actor permissions.

Description Summary:
An unauthenticated resource exhaustion vulnerability in ash_typescript allows attackers to crash the BEAM virtual machine by flooding the atom table with arbitrary field names.

Executive Summary:
A critical resource exhaustion vulnerability in ash_typescript allows unauthenticated attackers to cause a denial of service by crashing the underlying BEAM node.

Vulnerability Details

CVE-ID: CVE-2026-74837

Affected Software: ash-project ash_typescript

Affected Versions: 0.1.0 up to (excluding) 0.18.0

Vulnerability: The application utilizes String.to_atom/1 on user-supplied input within the FieldFormatter module without implementing length bounds or rate limits, allowing an unauthenticated attacker to exhaust the BEAM atom table. Because atoms in the BEAM virtual machine are not garbage collected, this leads to a node abort once the system limit is reached.

Business Impact

This vulnerability poses a significant risk to service availability, as it allows any unauthenticated network user to force a complete application crash. Given the CVSS score of 8.7, the potential for widespread service disruption is high, which could result in substantial operational downtime and loss of system integrity for any infrastructure relying on the affected library.

Remediation Plan

Immediate Action: Update the ash_typescript dependency to version 0.18.0 or later to ensure proper input handling and atom creation limits are enforced.

Proactive Monitoring: Review application logs for unusually high volumes of RPC requests or frequent node restarts that may indicate an attempt to trigger this exhaustion condition.

Compensating Controls: Implement strict rate limiting at the network or API gateway level to restrict the number of requests a single client can make, thereby reducing the velocity at which an attacker can exhaust the atom table.

Exploitation Status

Public Exploit Available: No — there is no confirmed public exploit in the available data.

Analyst Notes: As of September 1, 2026, there is no public information indicating active exploitation or a public proof-of-concept for this vulnerability. The flaw is inherently dangerous due to the nature of BEAM atom management, which makes the application highly susceptible to trivial denial of service attacks if left unpatched.

Analyst Recommendation

The severity of this issue is underscored by the ease with which an unauthenticated actor can destabilize the entire application environment. Administrators must prioritize updating to version 0.18.0 to eliminate the underlying logic flaw. Failure to apply this update leaves the service vulnerable to simple and highly effective denial of service attacks.