Security readout for executives and security teams
Plain-English summary
A publicly reachable .git directory can expose the ERP application's repository data without authentication. An attacker may reconstruct source code, revealing sensitive implementation details and potentially embedded secrets. The supplied record rates this critical, but the affected-version information is incomplete.
Executive priority
Treat this as an immediate exposure-assessment and containment priority for internet-facing Manacle ERP systems. Source-code disclosure can materially assist later attacks, while leaked credentials could affect connected services. Exact version scope and an official fix are not established in the supplied evidence.
Technical view
CVE-2026-84149 is a CWE-527 repository-exposure flaw in Manacle Technologies' Multi-tenant ERP System. Network access requires no privileges, user interaction, or special conditions. The CVSS 4.0 score is 9.2, reflecting high confidentiality impact to both the vulnerable system and connected systems, with no stated integrity or availability impact.
Likely exposure
Risk is concentrated in internet-accessible ERP deployments where web servers expose the application's .git directory. The bundle does not identify a meaningful affected version and reports a default status of unaffected, so asset-specific exposure cannot be determined from version matching alone.
Exploitation context
An unauthenticated remote party could retrieve repository metadata and associated files, potentially reconstructing application source code. This may expose architecture, credentials, or other sensitive material if present. The CVE is not listed as KEV, and the supplied sources provide no evidence of active exploitation.
Researcher notes
The record supplies CVSS 4.0 vector AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/SC:H and maps the issue to CWE-527. Product identification is broad, the version value is nonspecific, and no CPEs are provided. Confirm scope and remediation with vendor or CERT-In guidance; do not infer that every deployment is vulnerable.
Mitigation direction
- Check CERT-In and Manacle Technologies guidance for an authoritative remediation or fixed release.
- Remove or block public access to all .git directories and repository files.
- Review exposed repository contents for credentials, tokens, private keys, or sensitive configuration.
- Rotate any secrets that may have been stored in the exposed repository.
Validation and detection
- Inventory internet-facing Manacle ERP instances and identify their deployed versions.
- Verify externally that .git paths and repository artifacts are inaccessible.
- Review web access logs for historical requests targeting .git files or repository metadata.
- Confirm exposed secrets were identified, revoked, rotated, and removed from repository history where appropriate.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-527: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-84149 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.2 (4.0)
- Known Exploited
- No
- Published
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
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
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——CERT-InVulnerability scoring details
Base CVSS 4.0 score
9.2CriticalVector: 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
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://www.cert-in.org.in/s2cMainServlet?pageid=PUBVLNOTES01&VLCODE=CIVN-2026-0430CVE reference, CERT-In · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Exposure of Version-Control Repository to an Unauthorized Control Sphere
Exposure of Version-Control Repository to an Unauthorized Control Sphere represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.