CVE-2025-41086VulnerabilityPublished 2 Dec 2025

CVE-2025-41086: AMS Development GAMS · Insecure Direct Object Reference

Affects AMS Development GAMSSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 11% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
AMS Development Corp. GAMS	Affected =0	Fixed in–

AI-suggested

1. AMS Development Corp. should urgently redesign the license validation mechanism to use strong cryptographic algorithms (e.g., HMAC with SHA-256) instead of insecure checksums, ensuring license keys cannot be forged or tampered with. 2. Implement digital signatures for license keys, enabling verification of authenticity and integrity without exposing sensitive algorithms. 3. Deploy license usage monitoring and anomaly detection systems to identify unusual license generation or usage patterns indicative of abuse. 4. Restrict license key generation and validation processes to trusted environments with multi-factor authentication and strict access controls. 5. Encourage customers to regularly audit their license usage and report discrepancies promptly. 6. Until a patch is available, organizations should consider limiting exposure by isolating GAMS installations, restricting network access, and enforcing strict endpoint security controls. 7. Engage with AMS support channels for updates and potential workarounds. 8. Educate users about the risks of unauthorized license generation and enforce policies to prevent sharing or misuse of license keys.

Description

CVE-2025-41086 is a medium-severity vulnerability in AMS Development Corp. 's GAMS software licensing system. It involves an authorization bypass through a user-controlled key due to an insecure checksum algorithm used in license validation. Attackers can generate unlimited valid licenses without credentials or source code access, granting unrestricted use of GAMS's mathematical models and commercial solvers. The vulnerability requires no authentication or user interaction and can be exploited remotely. Although no known exploits are currently reported in the wild, the flaw poses significant risks to organizations relying on GAMS for critical mathematical and optimization tasks. European organizations using GAMS may face unauthorized usage and intellectual property theft. Mitigation requires AMS to update the licensing validation mechanism with a secure cryptographic approach and for users to monitor license usage closely. Countries with strong industrial, academic, and research sectors using GAMS are most likely affected.

Impact

For European organizations, the impact of CVE-2025-41086 can be substantial, especially for those relying on GAMS for critical mathematical modeling, optimization, and decision-making processes in sectors such as manufacturing, logistics, finance, energy, and research institutions. Unauthorized license generation can lead to unlicensed software use, resulting in financial losses for both AMS and its customers due to license revenue leakage. Furthermore, unrestricted access to GAMS's solvers may enable attackers to manipulate or misuse mathematical models, potentially affecting the integrity of business-critical computations and research outcomes. This could indirectly impact operational decisions, regulatory compliance, and competitive advantage. Additionally, organizations may face legal and contractual risks if software usage terms are violated. The vulnerability's ease of exploitation and lack of authentication requirements increase the risk of widespread abuse, particularly in environments where license enforcement is critical. Although no direct data confidentiality breach is indicated, the loss of control over software usage can have significant operational and financial repercussions.

Summary

CVE-2025-41086 is a vulnerability classified under CWE-639 (Authorization Bypass Through User-Controlled Key) affecting the licensing system of AMS Development Corp.'s GAMS software. GAMS is a high-level modeling system for mathematical optimization widely used in academia, industry, and research. The vulnerability arises because the license validator employs an insecure checksum algorithm to verify license keys. This checksum is predictable and reversible, allowing an attacker who understands the algorithm and license format to recalculate the checksum and generate valid license keys arbitrarily. Consequently, attackers can bypass all usage restrictions and gain full privileges to use GAMS's commercial solvers and mathematical models without valid credentials or access to the source code. The vulnerability requires no authentication or user interaction and can be exploited remotely, making it accessible to a wide range of threat actors. The CVSS 4.0 score is 6.9 (medium severity), reflecting the lack of direct impact on confidentiality or integrity but significant impact on availability and authorization controls. No patches or known exploits are currently available, indicating the need for proactive mitigation. The flaw undermines the licensing mechanism's integrity, potentially leading to widespread unauthorized use and loss of revenue for AMS and its customers.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 9 Dec 2025, 14:39 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats