Where
-Infinity
0

Juniper JunosJunos OS: SRX4600, SRX5000 Series: TCP packets with SYN/FIN or SYN/RST are transferred after enabling no-syn-check with Express Path

Risk 33
Severity
6.9
First published (updated )

Juniper JunosJunos OS: SRX 5000 Series with SPC2: Processing of specific crafted packets when ALG is enabled causes a transit traffic Denial of Service

Risk 33
Severity
8.7
EPSS
0.04%
First published (updated )

Juniper JunosSRX Series and MX Series: An FPC core is observed when IDP is enabled on the device and a specific malformed SSL packet is received

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: Policies that rely on JDPI-Decoder actions may fail open

Risk 27
Severity
5.3
First published (updated )

Juniper JunosJunos OS: SRX Series: The flow processing daemon (flowd) will crash when Unified Policies are used with IPv6 and certain dynamic applications are rejected by the device

Risk 43
Severity
7.5
First published (updated )
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Juniper JunosJunos OS: SRX Series and MX Series with SPC3: When IPsec VPN is configured iked will core when a specifically formatted payload is received

Risk 38
Severity
6.5
First published (updated )

Juniper JunosJunos OS: SRX Series and MX Series: Memory leak due to receipt of specially crafted SIP calls

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash if SIP ALG is enabled and a malformed SIP packet is received

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash if the SIP ALG is enabled and specific SIP messages are processed

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: A memory leak might be observed in IPsec VPN scenario leading to an FPC crash

Risk 43
Severity
7.5
First published (updated )
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Juniper JunosJunos OS: MX Series and SRX Series: The flow processing daemon (flowd) will crash when specific H.323 packets are received

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series, MX Series with SPC3: When an inconsistent NAT configuration exists and a specific CLI command is issued the SPC will reboot

Risk 32
Severity
5.5
First published (updated )

Juniper JunosJunos OS: SRX Series and MX Series: When specific valid SIP packets are received the PFE will crash

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: A flowd core will be observed when malformed GPRS traffic is processed

Risk 43
Severity
7.5
First published (updated )

Juniper JunosSRX Series: If Unified Threat Management (UTM) Enhanced Content Filtering (CF) is enabled and specific traffic is processed the PFE will crash

Risk 43
Severity
7.5
First published (updated )
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Juniper JunosJunos OS: SRX Series: Upon processing of a genuine packet the pkid process will crash during CMPv2 auto-re-enrollment

Risk 43
Severity
7.5
First published (updated )

Juniper JunosSRX5000 Series with SPC3, SRX4000 Series, and vSRX: When PowerMode IPsec is configured, the PFE will crash upon receipt of a malformed ESP packet

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX series: The PFE will crash when specific traffic is scanned by Enhanced Web Filtering safe-search

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: An FPC memory leak can occur in an APBR scenario

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: MX Series and SRX Series: When receiving a specific SIP packets stale call table entries are created which eventually leads to a DoS for all SIP traffic

Risk 27
Severity
5.3
First published (updated )
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Juniper JunosJunos OS: MX MS-MPC or MS-MIC, or SRX SPC crashes if it receives a SIP message with a specific contact header format

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: Denial of service vulnerability in flowd daemon upon receipt of a specific fragmented packet

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: MX Series and SRX Series: The flowd daemon will crash if the SIP ALG is enabled and specific SIP messages are processed

Risk 43
Severity
7.5
First published (updated )

Juniper JunosSRX Series and MX Series with SPC3: A high percentage of fragments might lead to high latency or packet drops

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS: SRX Series: The flowd process will crash if log session-close is configured and specific traffic is received

Risk 35
Severity
5.9
First published (updated )
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Juniper JunosJunos OS: SRX Series: Memory leak when querying Aggregated Ethernet (AE) interface statistics

Risk 43
Severity
7.5
First published (updated )

Juniper JunosJunos OS and Junos OS Evolved: Upon receipt of a specific BGP FlowSpec message network traffic may be disrupted.

Risk 73
Severity
10
First published (updated )

Juniper JunosJunos OS: Receipt of a specifically crafted malicious MPLS packet leads to a Junos kernel crash.

Risk 43
Severity
7.5
First published (updated )

ISC BINDImproper fetch cleanup sequencing in the resolver can cause named to crash

Risk 43
Severity
7.5
First published (updated )

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203