Vulnerability · CVE-2026-77526
sync 2026-11-02T23:03:50Z
Published Unknown date · sync 2026-11-02T23:03:50Z
Last checked Nov 3, 2026. A connected source was read within the last 7 days.
Open the advisory
Exploitation likelihood is not on this record for CVE-2026-77526. A missing EPSS score is not a low risk. Compare sync 2026-11-02T23:03:50Z with the linked advisory before you change production.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (sync 2026-11-02T23:03:50Z).
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- EPSS is missing. A missing score is not a low risk.
- Severity
- Unknown—
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- Not in the current FIRST EPSS dataset
- Remediation
- Version ranges on file
- Affected products
- packagist facturascripts/facturascripts
into those directories are served directly by Apache. Combined with not being in , the primitive escalates from arbitrary file write to remote code execution." -date: "2026-07-14" +date: "2026-11-02" pubdate: "2026-07-14" -affected_range: ">=2025.0.0 <=2026.2.0" -fixed_versions: [] -affected_versions: "All versions starting from 2025.0.0 up to 2026.2.0" -not_impacted: "" -solution: "Unfor
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- packagist facturascripts/facturascripts>=2025.0.0 <=2026.2.0
How to fix CVE-2026-77526
Upgrade
CVE-2026-77526 lists a fix boundary at 2026.2.0. Compare the installed build with that boundary before you change production.
Version check
Seen in >=2025.0.0 <=2026.2.0
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
Exploitation likelihood is not on this record for CVE-2026-77526. A missing EPSS score is not a low risk. Compare sync 2026-11-02T23:03:50Z with the linked advisory before you change production.
Which versions are affected?
Compare what you have installed with >=2025.0.0 <=2026.2.0. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS is absent from the current FIRST dataset. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Nov 3, 2026 · GitLab Advisory Database
Detected
into those directories are served directly by Apache. Combined with not being in , the primitive escalates from arbitrary file write to remote code execution." -date: "2026-07-14" +date: "2026-11-02" pubdate: "2026-07-14" -affected_range: ">=2025.0.0 <=2026.2.0" -fixed_versions: [] -affected_versions: "All versions starting from 2025.0.0 up to 2026.2.0" -not_impacted: "" -solution: "Unfor
Sources
- GitLab Advisory DatabasePackage advisorypackagist/facturascripts/facturascripts/GHSA-hgjx-r89m-m7v4.yml
into those directories are served directly by Apache. Combined with not being in , the primitive escalates from arbitrary file write to remote code execution." -date: "2026-07-14" +date: "2026-11-02" pubdate: "2026-07-14" -affected_range: ">=2025.0.0 <=2026.2.0" -fixed_versions: [] -affected_versions: "All versions starting from 2025.0.0 up to 2026.2.0" -not_impacted: "" -solution: "Unfor
gitlab.com
Freshness
Last verified in this catalog Nov 3, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.
- GitLab Advisory DatabaseNov 3, 2026