Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-33147: CWE-121: Stack-based Buffer Overflow in GenericMappingTools gmt

0
High
VulnerabilityCVE-2026-33147cvecve-2026-33147cwe-121
Published: Fri Mar 20 2026 (03/20/2026, 20:10:28 UTC)
Source: CVE Database V5
Vendor/Project: GenericMappingTools
Product: gmt

Description

GMT is an open source collection of command-line tools for manipulating geographic and Cartesian data sets. In versions from 6.6.0 and prior, a stack-based buffer overflow vulnerability was identified in the gmt_remote_dataset_id function within src/gmt_remote.c. This issue occurs when a specially crafted long string is passed as a dataset identifier (e.g., via the which module), leading to a crash or potential arbitrary code execution. This issue has been patched via commit 0ad2b49.

AI-Powered Analysis

AILast updated: 03/20/2026, 20:39:19 UTC

Technical Analysis

GenericMappingTools (GMT) is an open-source suite of command-line utilities widely used for processing geographic and Cartesian datasets. In versions 6.6.0 and earlier, a stack-based buffer overflow vulnerability (CWE-121) was discovered in the gmt_remote_dataset_id function located in src/gmt_remote.c. This function processes dataset identifiers, and when it receives an excessively long, specially crafted string, it fails to properly validate input length, leading to a buffer overflow on the stack. This memory corruption can cause the application to crash or, more critically, allow an attacker to execute arbitrary code with the privileges of the GMT process. The vulnerability requires local access (attack vector: local) but no privileges or user interaction, making it easier to exploit in environments where users have shell access. The vulnerability was assigned CVE-2026-33147 with a CVSS v3.1 score of 7.3, reflecting high severity due to its impact on availability (crash) and potential confidentiality and integrity (code execution). The issue has been addressed in a patch committed under ID 0ad2b49, which corrects the input handling to prevent overflow. No public exploits have been reported yet, but the nature of the vulnerability makes it a significant risk for affected systems. GMT is commonly used in scientific, environmental, and defense applications, where data integrity and availability are critical.

Potential Impact

The vulnerability poses a significant risk to organizations relying on GMT for geospatial data processing. Exploitation can lead to denial of service through application crashes, disrupting critical data workflows. More severely, arbitrary code execution could allow attackers to escalate privileges, manipulate sensitive geographic data, or establish persistence on affected systems. This can compromise the confidentiality and integrity of datasets, potentially impacting decision-making in sectors such as environmental monitoring, urban planning, defense, and research institutions. Since GMT is often deployed in Linux-based environments, local users or attackers with limited access could exploit this flaw to gain further control. The absence of required privileges or user interaction lowers the barrier for exploitation in multi-user or shared environments. Although no exploits are currently known in the wild, the vulnerability’s characteristics warrant urgent remediation to prevent future attacks.

Mitigation Recommendations

Organizations should immediately upgrade GMT to versions later than 6.6.0 where the vulnerability is patched. If upgrading is not immediately feasible, apply any available backported patches or mitigations from the GMT maintainers. Implement strict input validation and sanitization on dataset identifiers to prevent excessively long strings from being processed. Restrict local access to systems running GMT to trusted users only, and employ least privilege principles to limit potential exploitation impact. Monitor system logs for unusual crashes or suspicious activity related to GMT processes. Consider deploying runtime protections such as stack canaries, address space layout randomization (ASLR), and control flow integrity (CFI) to reduce exploitation likelihood. Regularly audit and update all geospatial software dependencies to maintain security hygiene.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-17T21:17:08.884Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bdacf5e32a4fbe5fcbbe12

Added to database: 3/20/2026, 8:24:21 PM

Last enriched: 3/20/2026, 8:39:19 PM

Last updated: 3/20/2026, 10:11:43 PM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses