Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-84149 – Sensitive Information Disclosure via Exposed .git Directory – Manacle Technologies

Be the first to know when new zero-days emerge:

Summary

CVE-2026-84149 is a critical information disclosure vulnerability affecting the Manacle Technologies Multi-tenant ERP System, caused by a publicly accessible .git directory on the application’s web server. An unauthenticated, remote attacker can browse or download the exposed repository metadata and reconstruct portions of the application’s source code. The vulnerability has been assigned a CVSS score of 9.2 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: The .git version-control directory used during development/deployment was left accessible under the web root, rather than being excluded from the publicly served application files.
  • Trigger conditions: No authentication, privileges, or user interaction are required — an attacker simply needs network access to the application’s web server and knowledge (or discovery) of the .git path.
  • Attack vector: Network-based (remote, unauthenticated HTTP requests to retrieve .git objects, logs, and configuration files).
  • Impact: Disclosure of repository metadata and version-control objects can allow an attacker to reconstruct application source code, potentially revealing embedded credentials, API keys, internal logic, and other sensitive artifacts that facilitate further attacks against the ERP platform.
  • Classification: CWE-527 – Exposure of Version-Control Repository to an Unauthorized Control Sphere.
  • This issue was disclosed alongside two related vulnerabilities in the same product — an unauthenticated arbitrary file upload leading to remote code execution (CVE-2026-84147) and an Insecure Direct Object Reference in an API endpoint exposing other users’ data (CVE-2026-84148) — indicating broader security hardening gaps in the platform’s deployment and access controls.

Affected software

  • Manacle Technologies Multi-tenant ERP System (specific affected version not disclosed by the vendor or CERT-In advisory at time of publication; default product status is listed as unaffected, with the impacted deployment version marked "affected" in the CVE record).

Severity

  • CVSS Score: 9.2 (Critical)
  • CVSS v4.0 Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:H/SI:N/SA:N
  • Attack Vector: Network | Attack Complexity: Low | Privileges Required: None | User Interaction: None | Confidentiality Impact: High

Mitigation and recommended actions

  • Immediate: No vendor patch version has been published yet; affected organizations should contact Manacle Technologies directly to obtain a fixed release or remediation guidance.
  • Workarounds / network mitigations (until patched):
    • Remove or restrict web server access to the .git directory (and any other version-control artifacts) on all internet-facing ERP deployments.
    • Configure the web server (e.g., via .htaccess, nginx location blocks, or equivalent) to deny all external requests to paths containing .git.
    • Audit deployment pipelines to ensure version-control directories are never copied into production web roots.
    • Rotate any credentials, API keys, or secrets that may have been present in the exposed repository history.
    • Given the related RCE (CVE-2026-84147) and IDOR (CVE-2026-84148) issues disclosed for this same product, review file upload validation and API authorization controls as part of a broader remediation effort.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge