Name: Vietnam CyStack Joint Stock Company
Address: Tan Hong Ha Complex, 317 Truong Chinh Street, Hanoi, Vietnam, 100000, VN
Telephone: (+84) 247 109 9656
Price range: Negotiable

Products & ServicesProducts & Services
SolutionsSolutions
PricingPricing
CompanyCompany
ResourcesResources

VulnScan

xmlsoft Security Vulnerabilities | CyStack CVE Database

Vulnerability	Exploitation status	Fix	Affected product	Published	Severity

`CVE-2026-86144`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityMedium
`CVE-2026-86143`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityMedium
`CVE-2026-86142`	Exploitation statusNot confirmed	FixYes	Affected productlibxml2	Published09/05/2026	SeverityMedium
`CVE-2026-86141`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityLow
`CVE-2026-86140`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityHigh
`CVE-2026-86139`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityMedium
`CVE-2026-86138`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/05/2026	SeverityMedium
`CVE-2026-86137`	Exploitation statusNot confirmed	FixYes	Affected productlibxml2	Published09/05/2026	SeverityLow
`CVE-2026-11979`Stack-Based Buffer Overflow in libxml2	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published06/29/2026	SeverityLow
`CVE-2026-6653`libxml2: Use after free in xmlParseInternalSubset via improper entity resolution handling	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published06/22/2026	SeverityHigh
`CVE-2026-6732`Libxml2: libxml2: denial of service via crafted xsd-validated document	Exploitation statusNot known exploited	FixNot confirmed	Affected productRed Hat Hardened Images	Published04/23/2026	SeverityMedium
`CVE-2026-0992`Libxml2: libxml2: denial of service via crafted xml catalogs	Exploitation statusNot known exploited	FixNot confirmed	Affected productRed Hat Hardened Images	Published01/15/2026	SeverityLow
`CVE-2026-0989`Libxml2: unbounded relaxng include recursion leading to stack overflow	Exploitation statusNot known exploited	FixNot confirmed	Affected productRed Hat Hardened Images	Published01/15/2026	SeverityLow
`CVE-2026-0990`Libxml2: libxml2: denial of service via uncontrolled recursion in xml catalog processing	Exploitation statusNot known exploited	FixNot confirmed	Affected productRed Hat Hardened Images	Published01/15/2026	SeverityMedium
`CVE-2025-9714`Stack overflow in libxml2	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published09/10/2025	SeverityMedium
`CVE-2025-8732`libxml2 xmlcatalog xmlParseSGMLCatalog recursion	Exploitation statusPublic exploit	FixNot confirmed	Affected productlibxml2	Published08/08/2025	SeverityMedium
`CVE-2025-7424`Libxslt: type confusion in xmlnode.psvi between stylesheet and source nodes	Exploitation statusNot known exploited	FixYes	Affected productlibxslt	Published07/10/2025	SeverityHigh
`CVE-2025-6170`Libxml2: stack buffer overflow in xmllint interactive shell command handling	Exploitation statusNot known exploited	FixYes	Affected productRed Hat Enterprise Linux 10	Published06/16/2025	SeverityLow
`CVE-2025-6021`Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2	Exploitation statusPublic exploit	FixYes	Affected productRed Hat Enterprise Linux 10	Published06/12/2025	SeverityHigh
`CVE-2025-32415`	Exploitation statusPublic exploit	FixYes	Affected productlibxml2	Published04/17/2025	SeverityLow
`CVE-2025-32414`	Exploitation statusPublic exploit	FixYes	Affected productlibxml2	Published04/08/2025	SeverityMedium
`CVE-2024-55549`	Exploitation statusPublic exploit	FixYes	Affected productlibxslt	Published03/14/2025	SeverityHigh
`CVE-2025-24855`	Exploitation statusNot known exploited	FixYes	Affected productlibxslt	Published03/14/2025	SeverityHigh
`CVE-2024-56171`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published02/18/2025	SeverityHigh
`CVE-2025-27113`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published02/18/2025	SeverityLow
`CVE-2025-24928`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published02/18/2025	SeverityHigh
`CVE-2022-49043`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published01/26/2025	SeverityHigh
`CVE-2024-40896`	Exploitation statusNot known exploited	FixYes	Affected productlibxml2	Published12/23/2024	SeverityCritical
`CVE-2024-34459`	Exploitation statusPublic exploit	FixNot confirmed	Affected productNot confirmed	Published05/13/2024	SeverityHigh
`CVE-2024-25062`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published02/04/2024	SeverityHigh
`CVE-2023-45322`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published10/06/2023	SeverityUnknown
`CVE-2023-39615`	Exploitation statusPublic exploit	FixNot confirmed	Affected productNot confirmed	Published08/29/2023	SeverityUnknown
`CVE-2023-28484`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published04/24/2023	SeverityMedium
`CVE-2023-29469`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published04/24/2023	SeverityMedium
`CVE-2022-40304`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published11/23/2022	SeverityHigh
`CVE-2022-40303`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published11/22/2022	SeverityHigh
`CVE-2016-3709`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published07/28/2022	SeverityUnknown
`CVE-2022-29824`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/03/2022	SeverityUnknown
`CVE-2022-23308`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published02/26/2022	SeverityHigh
`CVE-2021-30560`	Exploitation statusNot known exploited	FixYes	Affected productChrome	Published08/03/2021	SeverityHigh
`CVE-2021-3541`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published07/09/2021	SeverityUnknown
`CVE-2021-3516`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published06/01/2021	SeverityUnknown
`CVE-2021-3517`	Exploitation statusNot known exploited	FixNot confirmed	Affected productlibxml2	Published05/19/2021	SeverityHigh
`CVE-2021-3518`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published05/18/2021	SeverityUnknown
`CVE-2021-3537`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published05/14/2021	SeverityUnknown
`CVE-2020-24977`	Exploitation statusNot confirmed	FixYes	Affected productNot confirmed	Published09/03/2020	SeverityUnknown
`CVE-2020-7595`	Exploitation statusPublic exploit	FixNot confirmed	Affected productNot confirmed	Published01/21/2020	SeverityHigh
`CVE-2019-20388`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published01/21/2020	SeverityHigh
`CVE-2019-19956`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published12/24/2019	SeverityHigh
`CVE-2019-5815`	Exploitation statusNot confirmed	FixYes	Affected productChrome	Published12/11/2019	SeverityUnknown
`CVE-2019-18197`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published10/18/2019	SeverityHigh
`CVE-2019-13118`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published07/01/2019	SeverityMedium
`CVE-2019-13117`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published07/01/2019	SeverityMedium
`CVE-2019-11068`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published04/10/2019	SeverityCritical
`CVE-2017-15412`	Exploitation statusNot confirmed	FixNot confirmed	Affected productGoogle Chrome prior to 63.0.3239.84 unknown	Published08/28/2018	SeverityUnknown
`CVE-2016-9596`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published08/16/2018	SeverityUnknown
`CVE-2018-14567`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published08/16/2018	SeverityUnknown
`CVE-2016-9598`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published08/16/2018	SeverityUnknown
`CVE-2016-9597`	Exploitation statusNot confirmed	FixNot confirmed	Affected productlibxml2	Published07/30/2018	SeverityUnknown
`CVE-2018-14404`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published07/19/2018	SeverityMedium
`CVE-2017-18258`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/08/2018	SeverityUnknown
`CVE-2018-9251`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/04/2018	SeverityUnknown
`CVE-2017-7375`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published02/19/2018	SeverityCritical
`CVE-2017-7376`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published02/19/2018	SeverityUnknown
`CVE-2017-5130`	Exploitation statusNot known exploited	FixNot confirmed	Affected productGoogle Chrome prior to 62.0.3202.62	Published02/07/2018	SeverityHigh
`CVE-2017-16931`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published11/23/2017	SeverityUnknown
`CVE-2017-16932`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published11/23/2017	SeverityHigh
`CVE-2017-9050`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published05/18/2017	SeverityHigh
`CVE-2017-9049`	Exploitation statusPublic exploit	FixNot confirmed	Affected productNot confirmed	Published05/18/2017	SeverityHigh
`CVE-2017-9047`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/18/2017	SeverityUnknown
`CVE-2017-9048`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published05/18/2017	SeverityHigh
`CVE-2017-8872`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published05/10/2017	SeverityCritical
`CVE-2017-5029`	Exploitation statusNot confirmed	FixNot confirmed	Affected productGoogle Chrome prior to 57.0.2987.98 for Mac, Windows and Linux, and 57.0.2987.108 for Android	Published04/24/2017	SeverityUnknown
`CVE-2016-4483`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/11/2017	SeverityUnknown
`CVE-2017-5969`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/11/2017	SeverityUnknown
`CVE-2015-9019`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/05/2017	SeverityUnknown
`CVE-2016-9318`	Exploitation statusPublic exploit	FixNot confirmed	Affected productNot confirmed	Published11/16/2016	SeverityMedium
`CVE-2016-4658`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published09/25/2016	SeverityUnknown
`CVE-2016-5131`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published07/23/2016	SeverityHigh
`CVE-2016-4610`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published07/22/2016	SeverityUnknown
`CVE-2016-4607`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published07/22/2016	SeverityUnknown
`CVE-2016-4609`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published07/22/2016	SeverityUnknown
`CVE-2016-4608`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published07/22/2016	SeverityUnknown
`CVE-2016-4449`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published06/09/2016	SeverityUnknown
`CVE-2016-4447`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published06/09/2016	SeverityUnknown
`CVE-2016-4448`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published06/09/2016	SeverityUnknown
`CVE-2016-1684`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published06/05/2016	SeverityUnknown
`CVE-2016-1683`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published06/05/2016	SeverityUnknown
`CVE-2016-1834`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityHigh
`CVE-2016-1839`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-1836`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-1837`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-1838`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-1840`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-1833`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/20/2016	SeverityUnknown
`CVE-2016-3705`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/17/2016	SeverityUnknown
`CVE-2016-3627`	Exploitation statusNot known exploited	FixNot confirmed	Affected productNot confirmed	Published05/17/2016	SeverityHigh
`CVE-2015-6837`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/16/2016	SeverityUnknown
`CVE-2015-6838`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published05/16/2016	SeverityUnknown
`CVE-2015-8806`	Exploitation statusNot confirmed	FixNot confirmed	Affected productNot confirmed	Published04/13/2016	SeverityUnknown